Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
Go github.com/metal3-io/ironic-standalone-operator <= 0.7.2; >= 0.8.0, <= 0.8.1
Fixed in
0.7.30.8.2· Vendor fix available
Issue
Impact The Ironic Standalone Operator (IRSO) is the operator to maintain an Ironic deployment for Metal3. IRSO controller automatically adds its environment label to user-provided Secrets and ConfigMaps without the resource owner's consent. A high-privilege controller modifying user-owned resources constitutes an unauthorized integrity violation. Deployments running IrSO v0.7.0 through v0.8.1 that reference user-provided Secrets or ConfigMaps (TLS certificates, BMC CA, trusted CA) are affected. Patches Fixed in v0.9.0, v0.8.2, v0.7.3. Workarounds Manually add the environment label (ironic-standalone-operator.metal3.io/environment) to all user-provided Secrets and ConfigMaps before they are referenced in the Ironic resource. This prevents the controller from modifying them. Resources - https://github.com/metal3-io/ironic-standalone-operator/pull/619 - https://github.com/metal3-io/ironic-standalone-operator/pull/664 - https://github.com/metal3-io/ironic-standalone-operator/pull/665
Recommended action: Upgrade to 0.8.2 or 0.7.3 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/metal3-io/ironic-standalone-operator < 0.9.0
Fixed in
0.9.0· Vendor fix available
Issue
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
Recommended action: Upgrade to 0.9.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.