LUNAD3v AreaLoad up to 1a1103182ed63a06dde63d1712f3262eda19c3ec request.php phone sql injection
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
5.3 | $0-$5k | 0.06 |
A vulnerability was found in LUNAD3v AreaLoad up to 1a1103182ed63a06dde63d1712f3262eda19c3ec. It has been rated as critical. This issue affects some unknown processing of the file request.php. The manipulation of the argument phone
with an unknown input 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 weakness was disclosed 06/01/2017 as 264813c546dba03989ac0fc365f2022bf65e3be2. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2017-20195. The exploitation is known to be easy. 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.
By approaching the search of inurl:request.php it is possible to find vulnerable targets with Google Hacking.
Applying the patch 264813c546dba03989ac0fc365f2022bf65e3be2 is able to eliminate this problem. The bugfix is ready for download at github.com. A possible mitigation has been published immediately after the disclosure of the vulnerability. The advisory contains the following remark:
Added simple SQL injection prevention on request.php
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Partially
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: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Patch: 264813c546dba03989ac0fc365f2022bf65e3be2
Timeline
06/01/2017 🔍06/01/2017 🔍
10/27/2024 🔍
10/27/2024 🔍
Sources
Advisory: 264813c546dba03989ac0fc365f2022bf65e3be2Status: Confirmed
CVE: CVE-2017-20195 (🔍)
Entry
Created: 10/27/2024 10:23 AMChanges: 10/27/2024 10:23 AM (59)
Complete: 🔍
Cache ID: 18:56F:40
No comments yet. Languages: en.
Please log in to comment.