OpenStack Ironic before 29.0.1 can write unintended files to a target node disk during image handling (if a deployment was performed via the
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 24.1.3, 26.1.1, 29.0.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
OpenStack Ironic before 29.0.1 can write unintended files to a target node disk during image handling (if a deployment was performed via the API). A malicious project assigned as a node owner can provide a path to any local file (readable by ironic-conductor), which may then be written to the target node disk. This is difficult to exploit in practice, because a node deployed in this manner should never reach the ACTIVE state, but it still represents a danger in environments running with non-default, insecure configurations such as with automated cleaning disabled. The fixed versions are 24.1.3, 26.1.1, and 29.0.1.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- OpenStack Ironic
From 24 · fixed in 24.1.3; From 25 · fixed in 26.1.1; From 27 · fixed in 29.0.1
- ironicPyPI
fixed in 24.1.3; From 25.0.0 · fixed in 26.1.1; From 27.0.0 · fixed in 29.0.1
- ironicPyPI
fixed in 24.1.3
- ironicPyPI
From 25.0.0 · fixed in 26.1.1
- ironicPyPI
From 27.0.0 · fixed in 29.0.1