OpenResty up to 1.13.6.0 ngx.req.get_uri_args/ngx.req.get_post_args sql injection ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.9 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in OpenResty up to 1.13.6.0. The affected element is the function ngx.req.get_uri_args/ngx.req.get_post_args. The manipulation results in sql injection.
This vulnerability is reported as CVE-2018-9230. The attack can be launched remotely. No exploit exists.
The existence of this vulnerability is still disputed at present.
You should upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in OpenResty up to 1.13.6.0. Affected is the function ngx.req.get_uri_args/ngx.req.get_post_args. The manipulation with an unknown input leads to a sql injection vulnerability. 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:
In OpenResty before 1.13.6.1, URI parameters were obtained using the ngx.req.get_uri_args and ngx.req.get_post_args functions that ignore parameters beyond the hundredth one, which might allow remote attackers to bypass intended access restrictions or interfere with certain Web Application Firewall (ngx_lua_waf or X-WAF) products.
The bug was discovered 04/03/2018. The weakness was disclosed 04/02/2018 (Website). The advisory is shared for download at github.com. This vulnerability is traded as CVE-2018-9230 since 04/02/2018. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1505.
The real existence of this vulnerability is still doubted at the moment.
Upgrading to version 1.13.6.1 eliminates this vulnerability.
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: 9.0VulDB Meta Temp Score: 8.9
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 9.8
CNA 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
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: OpenResty 1.13.6.1
Timeline
04/02/2018 🔍04/02/2018 🔍
04/02/2018 🔍
04/03/2018 🔍
04/03/2018 🔍
08/05/2024 🔍
Sources
Advisory: github.comStatus: Not defined
Disputed: 🔍
CVE: CVE-2018-9230 (🔍)
GCVE (CVE): GCVE-0-2018-9230
GCVE (VulDB): GCVE-100-115572
Entry
Created: 04/03/2018 14:33Updated: 08/05/2024 11:18
Changes: 04/03/2018 14:33 (56), 01/20/2020 19:37 (1), 08/05/2024 11:18 (29)
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.