VulnerabilityPublished 4 Oct 2024Updated 5 Nov 2024

CVE-2024-47211: ironic

Affects ironicSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium · fixed in 26.1.0 : update ironic when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 26.1.0, 24.1.3, 23.0.3 +1

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade openstack/ironic to 26.1.0, 24.1.3, 23.0.3 or 21.4.4.

Affected software

Product	Affected	Fixed in
GitHubopenstack/ironic`pkg:github/openstack/ironic`Other threats	Affected <21.4.4 >=23.0.0 <23.0.3 >=24.0.0 <24.1.3 >=26.0.0 <26.1.0	Fixed in 21.4.4 23.0.3 24.1.3 26.1.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-47211, organizations should promptly upgrade OpenStack Ironic to the fixed versions: 21.4.4 or later, 23.0.3 or later, 24.1.3 or later, and 26.1.0 or later as applicable. If immediate upgrade is not feasible, administrators should implement strict network segmentation and firewall rules to restrict access to the Ironic API endpoints, limiting exposure to trusted networks and users only. Monitoring and logging of image_source URL requests can help detect anomalous or suspicious activity. Additionally, organizations can implement manual or automated validation of image sources outside of Ironic to verify checksums before provisioning. Employing image signing and verification mechanisms at the infrastructure level can further enhance trust in deployed images. Regular security audits and vulnerability scanning of OpenStack components should be conducted to identify and remediate similar issues proactively. Finally, maintaining an incident response plan tailored to cloud infrastructure disruptions will help minimize operational impact in case of exploitation.

Description

In OpenStack Ironic before 21.4.4, 22.x and 23.x before 23.0.3, 23.x and 24.x before 24.1.3, and 25.x and 26.x before 26.1.0, there is a lack of checksum validation of supplied image_source URLs when configured to convert images to a raw format for streaming.

Impact

The primary impact of CVE-2024-47211 is on the availability of services relying on OpenStack Ironic for bare metal provisioning. Attackers can supply malicious or corrupted image_source URLs that bypass integrity checks, potentially causing image streaming failures or provisioning disruptions. This can lead to denial of service conditions, delaying or preventing deployment of bare metal nodes. Organizations operating large-scale cloud infrastructure or data centers using OpenStack Ironic may experience operational downtime or degraded service quality. Although confidentiality and integrity of data are not directly compromised, the disruption of provisioning workflows can have cascading effects on service delivery and maintenance activities. The vulnerability could also increase operational costs due to troubleshooting and recovery efforts. Since exploitation requires no authentication and can be performed remotely, the attack surface is broad, especially in environments exposing the Ironic API endpoints. However, the absence of known exploits in the wild suggests limited immediate threat but warrants proactive mitigation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 08:48 UTC

Technical details

References

Community reviews

Related threats