OpenStack Ironic can return unredacted sensitive information when applying a PATCH to update fields in volume propertiesGHSA-j4cw-mcg2-2q78
MEDIUMFix: openstack/ironic@dd2df52GHSA-j4cw-mcg2-2q78 is a medium-severity (CVSS 6.8) CWE-212 vulnerability in ironic. A fix is available for ironic — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-j4cw-mcg2-2q78.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-j4cw-mcg2-2q78 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 384,993 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
ironic🐍ironic🐍ironic🐍ironicReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
In OpenStack Ironic through 35.0.1, when applying a PATCH to update fields in volume properties the user is authorized for, Ironic can return unredacted sensitive information (such as iSCSI credentials). The PATCH outcome is a security issue; the POST outcome is not a security issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | ironic | ≥ 17.0.0&&< 29.0.6 | 29.0.6pip install --upgrade 'ironic==29.0.6' |
| 🐍PyPI | ironic | ≥ 30.0.0&&< 32.0.2 | 32.0.2pip install --upgrade 'ironic==32.0.2' |
| 🐍PyPI | ironic | ≥ 33.0.0&&< 35.0.2 | 35.0.2pip install --upgrade 'ironic==35.0.2' |
| 🐍PyPI | ironic | ≥ 36.0.0&&< 37.0.1 | 37.0.1pip install --upgrade 'ironic==37.0.1' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ironic, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ironic to 29.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j4cw-mcg2-2q78 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.Source: Red Hat security advisory for GHSA-j4cw-mcg2-2q78 (CC BY 4.0)
Frequently Asked Questions
Is GHSA-j4cw-mcg2-2q78 in your dependencies?
Find it across PyPI, including transitive dependencies.