Approved changes feed: RSS · Atom

cpe:2.3:a:metal3:ironic-image:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorMetal3 (53a88cab-2da3-576c-be4f-7b89ec502184)
ProductIronic Image (81f45003-fb38-52cb-b685-1e69a624a21c)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/metal3-io/ironic-image purl2cpe 2026-06-01 10:13:06.017121

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2023-40585 vulnerable 2026-06-08 06:11:03.696239 Unauthenticated access to Ironic API
HIGH (7.3)
ironic-image is a container image to run OpenStack Ironic as part of Metal³. Prior to version capm3-v1.4.3, if Ironic is not deployed with TLS and it does not have API and Conductor split into separate services, access to the API is not protected by any authentication. Ironic API is also listening in host network. In case the node is not behind a firewall, the API could be accessed by anyone via network without authentication. By default, Ironic API in Metal3 is protected by TLS and basic authentication, so this vulnerability requires operator to configure API without TLS for it to be vulnerable. TLS and authentication however should not be coupled as they are in versions prior to capm3-v1.4.3. A patch exists in versions capm3-v1.4.3 and newer. Some workarounds are available. Either configure TLS for Ironic API (`deploy.sh -t ...`, `IRONIC_TLS_SETUP=true`) or split Ironic API and Conductor via configuration change (old implementation, not recommended). With both workarounds, services are configured with httpd front-end, which has proper authentication configuration in place.
Published: 2023-08-25T20:31:50.639Z
Updated: 2024-10-02T14:43:47.455Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.