Headline
GHSA-c98h-7hp9-v9hq: Bare Metal Operator (BMO) can expose any secret from other namespaces via BMCEventSubscription CRD
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
Credits
Metal3 Security Team thanks WHALEEYE and debuggerchen of Lab for Internet and Security Technology for responsible vulnerability disclosure.
Package
gomod github.com/metal3-io/baremetal-operator/apis (Go)
Affected versions
= 0.9.0
<= 0.8.0
Patched versions
0.9.1
0.8.1
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.
References
- GHSA-c98h-7hp9-v9hq
- metal3-io/baremetal-operator#2321
- metal3-io/baremetal-operator#2322
- metal3-io/baremetal-operator@19f8443
- https://github.com/metal3-io/metal3-docs/blob/main/design/baremetal-operator/bmc-events.md
Published to the GitHub Advisory Database
Mar 17, 2025
Last updated
Mar 17, 2025