Skip to content
Fencer Intel
medium 4.3

GHSA-7cwm-fpfh-rrch json

Ironic Standalone Operator's prometheus metrics exporter bound to all interfaces

published 5mo ago modified 4mo ago also GO-2026-5215

cvss
4.3
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

## 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

- https://github.com/metal3-io/ironic-standalone-operator/pull/635

Patch / fix

  • go github.com/metal3-io/ironic-standalone-operator 0.9.0

Is GHSA-7cwm-fpfh-rrch in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
GitHub 3.1 4.3 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/metal3-io/ironic-standalone-operator
<0.9.0
0.9.0

Classification

Weakness
  • CWE-668 Exposure of Resource to Wrong Sphere

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.