Discover the SQL-injection vulnerability in openstack-ironic-inspector versions excluding 5.0.2, 6.0.3, 7.2.4, 8.0.3, and 8.2.1. Learn about the impact, affected systems, and mitigation steps.
A security issue has been detected in all versions of openstack-ironic-inspector except for 5.0.2, 6.0.3, 7.2.4, 8.0.3, and 8.2.1. The vulnerability involves a SQL-injection vulnerability found in the node_cache.find_node() function of openstack-ironic-inspector. This particular function executes a SQL query using unfiltered data obtained from a server that reports inspection results through a POST request sent to the /v1/continue endpoint. Since the API lacks authentication, an attacker with network access to the system running ironic-inspector could potentially exploit this flaw. It is important to note that given how ironic-inspector utilizes the query results, it is unlikely that any data could be accessed. However, an attacker can manipulate the data to cause a denial of service.
Understanding CVE-2019-10141
This section provides insights into the impact and technical details of CVE-2019-10141.
What is CVE-2019-10141?
CVE-2019-10141 is a SQL-injection vulnerability found in the node_cache.find_node() function of openstack-ironic-inspector, affecting various versions of the software.
The Impact of CVE-2019-10141
The vulnerability has a CVSS base score of 8.3 (High severity) with a low attack complexity and network vector. It can lead to a denial of service attack due to the lack of authentication in the API.
Technical Details of CVE-2019-10141
This section delves into the vulnerability description, affected systems, versions, and exploitation mechanism.
Vulnerability Description
The SQL-injection vulnerability in node_cache.find_node() function allows attackers to manipulate unfiltered data obtained from inspection results, potentially leading to a denial of service.
Affected Systems and Versions
Exploitation Mechanism
The vulnerability can be exploited by an attacker with network access to the system running ironic-inspector due to the lack of authentication in the API.
Mitigation and Prevention
This section outlines the steps to mitigate and prevent the exploitation of CVE-2019-10141.
Immediate Steps to Take
Long-Term Security Practices
Patching and Updates