Laravel 5.4.15 save.php dhx_user/dhx_version Error sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in Laravel 5.4.15. This vulnerability affects unknown code of the file save.php. The manipulation of the argument dhx_user/dhx_version as part of Parameter results in sql injection (Error). This vulnerability is cataloged as CVE-2018-6330. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability, which was classified as critical, was found in Laravel 5.4.15. Affected is an unknown code block of the file save.php. The manipulation of the argument dhx_user/dhx_version as part of a Parameter leads to a sql injection vulnerability (Error). CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
Laravel 5.4.15 is vulnerable to Error based SQL injection in save.php via dhx_user and dhx_version parameters.
The bug was discovered 01/26/2018. The weakness was shared 03/28/2019. This vulnerability is traded as CVE-2018-6330 since 01/26/2018. It is possible to launch the attack remotely. The requirement for exploitation is a authentication. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1505.
The vulnerability was handled as a non-public zero-day exploit for at least 426 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:save.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.
Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.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
Name: ErrorClass: Sql injection / Error
CWE: 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
01/26/2018 🔍01/26/2018 🔍
03/28/2019 🔍
03/29/2019 🔍
08/17/2023 🔍
Sources
Advisory: itblog.gbonanno.deStatus: Not defined
CVE: CVE-2018-6330 (🔍)
GCVE (CVE): GCVE-0-2018-6330
GCVE (VulDB): GCVE-100-132564
Entry
Created: 03/29/2019 06:57Updated: 08/17/2023 13:28
Changes: 03/29/2019 06:57 (55), 05/22/2020 16:08 (1), 08/17/2023 13:28 (3)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.