Ironic Standalone Operator's prometheus metrics exporter bound to all interfacesGHSA-7cwm-fpfh-rrch
MEDIUMFix: metal3-io/ironic-standalone-operator#635GHSA-7cwm-fpfh-rrch is a medium-severity (CVSS 4.3) vulnerability in github.com/metal3-io/ironic-standalone-operator. A fix is available for github.com/metal3-io/ironic-standalone-operator — see the affected versions and patch details below.
Real-World Exposure
github.com/metal3-io/ironic-standalone-operatorReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
The Ironic Standalone Operator (IRSO) is the operator to maintain an Ironic deployment for Metal3. The Prometheus metrics exporter binds to 0.0.0.0 (all network interfaces) by default with no authentication. The default config is disabled. If enabled, this exposes operational metrics to any host on adjacent networks. Deployments running IrSO v0.7.0 through v0.8.1 with the Prometheus exporter enabled are affected. Versions prior to v0.7.0 do not have the Prometheus exporter feature.
Patches
The exporter now exposes a configurable bindAddress field. Users should upgrade to v0.9.0 or later.
Workarounds
Users on older versions than v0.9.0 should use host-level firewall rules (iptables/nftables) to restrict access to the metrics port from unintended networks, or disable the metrics service.
Resources
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/metal3-io/ironic-standalone-operator | all versions | 0.9.0go get github.com/metal3-io/ironic-standalone-operator@v0.9.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/metal3-io/ironic-standalone-operator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/metal3-io/ironic-standalone-operator to 0.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7cwm-fpfh-rrch 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.
Frequently Asked Questions
Is GHSA-7cwm-fpfh-rrch in your dependencies?
Find it across Go, including transitive dependencies.