PvPGN Stats 2.4.6 ladder/stats.php sort_direction sql injection

Summaryinfo

A vulnerability identified as critical has been detected in PvPGN Stats 2.4.6. The impacted element is an unknown function of the file ladder/stats.php. This manipulation of the argument sort_direction as part of Parameter causes sql injection. This vulnerability is handled as CVE-2017-18290. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in PvPGN Stats 2.4.6. It has been declared as critical. Affected by this vulnerability is some unknown functionality of the file ladder/stats.php. The manipulation of the argument sort_direction as part of a Parameter leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

An issue was discovered in PvPGN Stats 2.4.6. SQL Injection exists in ladder/stats.php via the GET sort_direction parameter.

The bug was discovered 09/19/2017. The weakness was released 06/12/2018 (Website). The advisory is shared at rchase.com. This vulnerability is known as CVE-2017-18290 since 06/12/2018. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 266 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:ladder/stats.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Entries connected to this vulnerability are available at VDB-119398, VDB-119399, VDB-119400 and VDB-119402. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• PvPGN Stats

Version

• 2.4.6

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion