PvPGN Stats 2.4.6 ladder/stats.php game sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in PvPGN Stats 2.4.6. It has been rated as critical. Impacted is an unknown function of the file ladder/stats.php. The manipulation of the argument game as part of Parameter leads to sql injection. This vulnerability is traded as CVE-2017-18288. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in PvPGN Stats 2.4.6 and classified as critical. This issue affects an unknown function of the file ladder/stats.php. The manipulation of the argument game as part of a Parameter leads to a sql injection vulnerability. Using CWE to declare the problem leads to 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. Impacted is 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 game parameter.
The bug was discovered 09/19/2017. The weakness was shared 06/12/2018 (Website). It is possible to read the advisory at rchase.com. The identification of this vulnerability is CVE-2017-18288 since 06/12/2018. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.
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.
The entries VDB-119398, VDB-119400, VDB-119401 and VDB-119402 are related to this item. Be aware that VulDB is the high quality source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
09/19/2017 🔍06/12/2018 🔍
06/12/2018 🔍
06/12/2018 🔍
06/13/2018 🔍
02/18/2020 🔍
Sources
Advisory: rchase.comStatus: Not defined
CVE: CVE-2017-18288 (🔍)
GCVE (CVE): GCVE-0-2017-18288
GCVE (VulDB): GCVE-100-119399
See also: 🔍
Entry
Created: 06/13/2018 08:30Updated: 02/18/2020 14:08
Changes: 06/13/2018 08:30 (58), 02/18/2020 14:08 (1)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.