openstack-ironic-inspector up to 8.2.0 /v1/continue node_cache.find_node SQL sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in openstack-ironic-inspector up to 5.0.1/6.0.2/7.2.3/8.0.2/8.2.0 and classified as problematic. The impacted element is the function node_cache.find_node of the file /v1/continue. Performing a manipulation results in sql injection (SQL).
This vulnerability is identified as CVE-2019-10141. The attack can be initiated remotely. There is not any exploit available.
The affected component should be upgraded.
Details
A vulnerability, which was classified as problematic, was found in openstack-ironic-inspector up to 5.0.1/6.0.2/7.2.3/8.0.2/8.2.0 (Cloud Software). This affects the function node_cache.find_node of the file /v1/continue. The manipulation with an unknown input leads to a sql injection vulnerability (SQL). 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 availability. The summary by CVE is:
A vulnerability was found in openstack-ironic-inspector all versions excluding 5.0.2, 6.0.3, 7.2.4, 8.0.3 and 8.2.1. A SQL-injection vulnerability was found in openstack-ironic-inspector's node_cache.find_node(). This function makes a SQL query using unfiltered data from a server reporting inspection results (by a POST to the /v1/continue endpoint). Because the API is unauthenticated, the flaw could be exploited by an attacker with access to the network on which ironic-inspector is listening. Because of how ironic-inspector uses the query results, it is unlikely that data could be obtained. However, the attacker could pass malicious data and create a denial of service.
The weakness was released 07/30/2019 as not defined bug report (Bugzilla). The advisory is shared at bugzilla.redhat.com. This vulnerability is uniquely identified as CVE-2019-10141 since 03/27/2019. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
Upgrading to version 5.0.2, 6.0.3, 7.2.4, 8.0.3 or 8.2.1 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.5
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.1
NVD Vector: 🔍
CNA Base Score: 8.3
CNA Vector (Red Hat, Inc.): 🔍
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: SQLClass: Sql injection / SQL
CWE: 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: openstack-ironic-inspector 5.0.2/6.0.3/7.2.4/8.0.3/8.2.1
Timeline
03/27/2019 🔍07/30/2019 🔍
07/31/2019 🔍
11/14/2023 🔍
Sources
Advisory: RHSA-2019:2505Status: Not defined
Confirmation: 🔍
CVE: CVE-2019-10141 (🔍)
GCVE (CVE): GCVE-0-2019-10141
GCVE (VulDB): GCVE-100-138981
Entry
Created: 07/31/2019 08:24Updated: 11/14/2023 09:13
Changes: 07/31/2019 08:24 (59), 07/15/2020 18:57 (1), 11/14/2023 09:09 (4), 11/14/2023 09:13 (12)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.