CVE-2025-29781

Source
https://nvd.nist.gov/vuln/detail/CVE-2025-29781
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2025-29781.json
JSON Data
https://api.test.osv.dev/v1/vulns/CVE-2025-29781
Aliases
Published
2025-03-17T22:15:14Z
Modified
2025-03-18T18:41:59.688112Z
Summary
[none]
Details

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. Prior to versions 0.8.1 and 0.9.1, an adversary Kubernetes account with only namespace level roles (e.g. a tenant controlling a namespace) may create a BMCEventSubscription in his authorized namespace and then load Secrets from his unauthorized namespaces to his authorized namespace via the Baremetal Operator, causing Secret Leakage. The patch makes BMO refuse to read Secrets from other namespace than where the corresponding BMH resource is. The patch does not change the BMCEventSubscription API in BMO, but stricter validation will fail the request at admission time. It will also prevent the controller reading such Secrets, in case the BMCES CR 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. As a workaround, the 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

Affected packages

Git / github.com/metal3-io/baremetal-operator

Affected ranges

Type
GIT
Repo
https://github.com/metal3-io/baremetal-operator
Events
Introduced
0 Unknown introduced commit / All previous commits are affected
Fixed

Affected versions

apis/v0.*

apis/v0.1.0
apis/v0.1.1
apis/v0.1.2
apis/v0.2.0
apis/v0.3.0
apis/v0.3.0-rc.0
apis/v0.3.1
apis/v0.4.0
apis/v0.5.0
apis/v0.7.0-rc.0
apis/v0.8.0-rc.0
apis/v0.9.0

Other

before-rename

capm3-v0.*

capm3-v0.3.0
capm3-v0.3.2
capm3-v0.4.0
capm3-v0.4.1
capm3-v0.4.3
capm3-v0.5.0
capm3-v0.5.1
capm3-v0.5.2
capm3-v0.5.3
capm3-v0.5.4
capm3-v0.5.5

capm3-v1.*

capm3-v1.1.0
capm3-v1.1.1
capm3-v1.1.2

pkg/hardwareutils/v0.*

pkg/hardwareutils/v0.1.0
pkg/hardwareutils/v0.1.1
pkg/hardwareutils/v0.1.2
pkg/hardwareutils/v0.2.0
pkg/hardwareutils/v0.3.0
pkg/hardwareutils/v0.3.0-rc.0
pkg/hardwareutils/v0.3.1
pkg/hardwareutils/v0.4.0
pkg/hardwareutils/v0.5.0
pkg/hardwareutils/v0.7.0-rc.0
pkg/hardwareutils/v0.8.0-rc.0
pkg/hardwareutils/v0.9.0

test/v0.*

test/v0.5.0
test/v0.7.0-rc.0
test/v0.8.0-rc.0
test/v0.9.0

v0.*

v0.1.0
v0.1.1
v0.1.2
v0.2.0
v0.3.0
v0.3.0-rc.0
v0.3.1
v0.4.0
v0.5.0
v0.7.0-rc.0
v0.8.0-rc.0
v0.9.0