GHSA-j4cw-mcg2-2q78 is a medium-severity (CVSS 6.8) CWE-212 vulnerability in ironic. O3 Security confirms whether GHSA-j4cw-mcg2-2q78 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
OpenStack Ironic can return unredacted sensitive information when applying a PATCH to update fields in volume properties
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.
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.6 |
| 🐍PyPI | ironic | ≥ 30.0.0&&< 32.0.2 | 32.0.2 |
| 🐍PyPI | ironic | ≥ 33.0.0&&< 35.0.2 | 35.0.2 |
| 🐍PyPI | ironic | ≥ 36.0.0&&< 37.0.1 | 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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.
How O3 protects you
O3 pinpoints whether GHSA-j4cw-mcg2-2q78 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-j4cw-mcg2-2q78. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-j4cw-mcg2-2q78 in your dependencies?
O3 detects GHSA-j4cw-mcg2-2q78 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.