GitHub Advisoryadvisory · Go

GHSA-c98h-7hp9-v9hq Bare Metal Operator (BMO) can expose any secret from other namespaces via BMCEventSubscription CRD

MEDIUM Published 2025-03-17 Modified 2025-03-19 Official page ↗
Aliases
CVE-2025-29781
Ecosystem
Go
Packages
github.com/metal3-io/baremetal-operator/apis
Severity
Moderate
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Weaknesses
CWE-200, CWE-653
Reviewed
2025-03-17

Affected packages

• Go github.com/metal3-io/baremetal-operator/apis: >= 0.9.0, < 0.9.1 → fixed in 0.9.1 • Go github.com/metal3-io/baremetal-operator/apis: < 0.8.1 → fixed in 0.8.1

Description

Impact The Bare Metal Operator (BMO) implements a Kubernetes API for managing bare metal hosts in Metal3. Baremetal Operator enables users to load Secret from arbitrary namespaces upon deployment of the namespace scoped Custom Resource `BMCEventSubscription` (BMCES). An adversary Kubernetes account with only namespace level roles (e.g. a tenant controlling a namespace) may create a BMCES in their authorized namespace and then load Secrets from their unauthorized namespaces to their authorized namespace via the Baremetal Operator controller's cluster scoped privileges, causing Secret leakage. Patches The patch makes BMO refuse to read Secrets from other namespace than where the corresponding Bare Metal Host (BMH) resource is. The patch does not change the `BMCEventSubscription` API in BMO, but stricter validation will deny the request at admission time. It will also prevent the controller reading such Secrets, in case the BMCES resource has already been deployed. The issue exists for all versions of BMO, and is patched in BMO releases v0.9.1 and v0.8.1. Prior upgrading to patched BMO version, duplicate any existing Secret pointed to by `BMCEventSubscription`'s `httpHeadersRef` to the same namespace where the corresponding BMH exists. After upgrade, remove the old Secrets. Workarounds Operator can configure BMO RBAC to be namespace scoped, instead of cluster scoped, to prevent BMO from accessing Secrets from other namespaces, and/or use `WATCH_NAMESPACE` configuration option to limit BMO to single namespace. References • patch to main • patch to release-0.9 • patch to release-0.8 • BMCEventSubscription design document Credits Metal3 Security Team thanks WHALEEYE and debuggerchen of Lab for Internet and Security Technology for responsible vulnerability disclosure.

Related

Alias · CVE (1)

  • CVE-2025-29781 The Bare Metal Operator (BMO) implements a Kubernetes API for managing bare metal hosts in Metal3. vulnerability

Weakness · CWE (2)

  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor weakness
  • CWE-653 Improper Isolation or Compartmentalization weakness

References