Skip to content
Noroxi
CVE-2019-10141· NVD / CVE Program· CNA redhat

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 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.

CriticalCVSS 9.1 · v3.0—No exploit Fix available
Published
Jul 30, 2019
Updated
Jun 16, 2026
EPSS
2.5% · 84th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

37

Monitor

Low priority for now.

CVSS
36 / 40 · 9.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.5%

CNA vs NVD score

NVD
9.1
CNA · redhat
8.3
0.8 point gap

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
openstackironic-inspector
redhatopenstack
redhatenterprise linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • openstack ironic-inspectorbefore 5.0.2
  • openstack ironic-inspector5.1.0 and later · before 6.0.3
  • openstack ironic-inspector6.1.0 and later · before 7.2.4
  • openstack ironic-inspector8.0.0 and later · before 8.0.3
  • openstack ironic-inspector8.1.0 and later · before 8.2.1
  • redhat openstack10
  • redhat openstack13
  • redhat openstack14
  • redhat openstack9

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • RedHat openstack-ironic-inspector

    • all 5.0.x up to, excluding 5.0.2, all 6.0.x up to, excluding 6.0.3, all 7.2.x up to, excluding 7.2.4, all 8.0.3 up to, excluding 8.0.3, 8.2.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12ironic-inspectorbefore 8.0.0-38.0.0-3
PyPIironic-inspectorfrom 5.1.0 · before 6.0.36.0.3
PyPIironic-inspectorfrom 6.1.0 · before 7.2.47.2.4
PyPIironic-inspectorfrom 8.0.0 · before 8.0.38.0.3
PyPIironic-inspectorfrom 8.1.0 · before 8.2.18.2.1
PyPIironic-inspectorbefore 5.0.25.0.2
Red Hat:openstack-director:9::el7openstack-ironic-inspectorbefore 0:3.2.2-5.el7ost0:3.2.2-5.el7ost
Red Hat:openstack-director:9::el7openstack-ironic-inspector-docbefore 0:3.2.2-5.el7ost0:3.2.2-5.el7ost
Red Hat:openstack:10::el7openstack-ironic-inspectorbefore 0:4.2.2-6.el7ost0:4.2.2-6.el7ost
Red Hat:openstack:13::el7openstack-ironic-inspectorbefore 0:7.2.3-3.el7ost0:7.2.3-3.el7ost
Red Hat:openstack:14::el7openstack-ironic-inspectorbefore 0:8.0.3-0.20190420013817.el7ost0:8.0.3-0.20190420013817.el7ost

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:ironic-inspector8.0.0-3 · Debian:12Package registry (OSV)
PyPI:ironic-inspector5.0.2Package registry (OSV)
PyPI:ironic-inspector6.0.3Package registry (OSV)
PyPI:ironic-inspector7.2.4Package registry (OSV)
PyPI:ironic-inspector8.0.3Package registry (OSV)
PyPI:ironic-inspector8.2.1Package registry (OSV)
red hat:openstack-ironic-inspector0:8.0.3-0.20190420013817.el7ost · Red Hat:openstack:14::el7Package registry (OSV)
red hat:openstack-ironic-inspector-doc0:3.2.2-5.el7ost · Red Hat:openstack-director:9::el7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

nvd-primary

Root cause

The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const owner = req.query.owner;const rows = await db.query(  "SELECT * FROM files WHERE owner = '" + owner + "'");

Fixed

ts
const owner = req.query.owner;const rows = await db.query(  "SELECT * FROM files WHERE owner = $1",  [owner]);

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records