CVE-2025-29781: Github.com/metal3 io/baremetal operator/apis Bare Metal Operator (BMO) Can Vulnerability

MODERATE
Advisory Identifier: GHSA-c98h-7hp9-v9hq
CVSS 6.5
CWE-200 CWE-653
Published
Advisory Summary

CVE-2025-29781 is a MODERATE (CVSS 6.5) bare metal operator (bmo) can vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Github.com/metal3 io/baremetal operator/apis libraries in the Go ecosystem. The issue involves bare metal operator (bmo) can expose any secret from other namespaces via bmceventsubscription crd. Remediation is available by upgrading affected packages to version 0.9.1, 0.8.1.

CVE-2025-29781 at a Glance

CVE Identifier CVE-2025-29781
GHSA Identifier GHSA-c98h-7hp9-v9hq
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product Github.com/metal3 io/baremetal operator/apis
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2025-29781

To remediate this vulnerability, upgrade all affected Github.com/metal3 io/baremetal operator/apis dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/metal3-io/baremetal-operator/apis fixed: 0.9.1
Upgrade github.com/metal3-io/baremetal-operator/apis to 0.9.1
github.com/metal3-io/baremetal-operator/apis fixed: 0.8.1
Upgrade github.com/metal3-io/baremetal-operator/apis to 0.8.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/metal3-io/baremetal-operator/apis

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-29781, inspect your project dependencies for Github.com/metal3 io/baremetal operator/apis:

inspect dependencies for github.com/metal3-io/baremetal-operator/apis

Analyze the terminal output to locate any version of Github.com/metal3 io/baremetal operator/apis in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.9.1), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. In Github.com/metal3 io/baremetal operator/apis, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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](https://github.com/metal3-io/baremetal-operator/commit/19f8443b1fe182f76dd81b43122e8dd102f8b94c) - [patch to release-0.9](https://github.com/metal3-io/baremetal-operator/pull/2321) - [patch to release-0.8](https://github.com/metal3-io/baremetal-operator/pull/2322) - [BMCEventSubscription design document](https://github.com/metal3-io/metal3-docs/blob/main/design/baremetal-operator/bmc-events.md) ### Credits Metal3 Security Team thanks [WHALEEYE](https://github.com/WHALEEYE) and [debuggerchen](https://github.com/debuggerchen) of [Lab for Internet and Security Technology](https://users.cs.northwestern.edu/~list/) for responsible vulnerability disclosure.

CVE-2025-29781 Affected Github.com/metal3 io/baremetal operator/apis Versions

2 component(s)
Fixed Versions:
0.9.10.8.1
Product / Package Ecosystem Affected Versions Fixed Version
github.com/metal3-io/baremetal-operator/apis
Go
≥ 0.9.0
< 0.9.1
All 1 versions
0.9.0
0.9.1
github.com/metal3-io/baremetal-operator/apis
Go
< 0.8.1
0.8.1

References

Frequently Asked Questions

What is CVE-2025-29781?
CVE-2025-29781 is a security vulnerability in Github.com/metal3 io/baremetal operator/apis involving Bare Metal Operator (BMO) can expose any secret from other namespaces via BMCEventSubscription CRD under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which Github.com/metal3 io/baremetal operator/apis versions are affected?
Affected versions include releases prior to 0.9.1, 0.8.1 across affected packages: github.com/metal3-io/baremetal-operator/apis.
What version fixes CVE-2025-29781?
Upgrading to 0.9.1, 0.8.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/metal3-io/baremetal-operator/apis affected?
Yes, github.com/metal3-io/baremetal-operator/apis is affected in releases prior to 0.9.1, 0.8.1. Upgrade your dependency to 0.9.1, 0.8.1 or later.
What is the CVSS score of CVE-2025-29781?
CVE-2025-29781 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N.
What CWE is associated with CVE-2025-29781?
CVE-2025-29781 is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).
How can I check Go dependencies for CVE-2025-29781?
Run the dependency tree command: 'inspect dependencies for github.com/metal3-io/baremetal-operator/apis'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-c98h-7hp9-v9hq",
  "modified" : "2025-03-19T14:59:19Z",
  "published" : "2025-03-17T21:26:14Z",
  "aliases" : [ "CVE-2025-29781" ],
  "summary" : "Bare Metal Operator (BMO) can expose any secret from other namespaces via BMCEventSubscription CRD",
  "details" : "### Impact\n\nThe Bare Metal Operator (BMO) implements a Kubernetes API for managing bare metal hosts in Metal3. \n\nBaremetal 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.\n\n### Patches\n\nThe 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.\n\nThe 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.\n\n### Workarounds\n\nOperator 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.\n\n### References\n\n- [patch to main](https://github.com/metal3-io/baremetal-operator/commit/19f8443b1fe182f76dd81b43122e8dd102f8b94c)\n- [patch to release-0.9](https://github.com/metal3-io/baremetal-operator/pull/2321)\n- [patch to release-0.8](https://github.com/metal3-io/baremetal-operator/pull/2322)\n- [BMCEventSubscription design document](https://github.com/metal3-io/metal3-docs/blob/main/design/baremetal-operator/bmc-events.md)\n\n### Credits\n\nMetal3 Security Team thanks [WHALEEYE](https://github.com/WHALEEYE) and [debuggerchen](https://github.com/debuggerchen) of [Lab for Internet and Security Technology](https://users.cs.northwestern.edu/~list/) for responsible vulnerability disclosure.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/metal3-io/baremetal-operator/apis"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.9.0"
      }, {
        "fixed" : "0.9.1"
      } ]
    } ],
    "versions" : [ "0.9.0" ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/metal3-io/baremetal-operator/apis"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.8.1"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.8.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/metal3-io/baremetal-operator/security/advisories/GHSA-c98h-7hp9-v9hq"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-29781"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/metal3-io/baremetal-operator/pull/2321"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/metal3-io/baremetal-operator/pull/2322"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/metal3-io/baremetal-operator/commit/19f8443b1fe182f76dd81b43122e8dd102f8b94c"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/metal3-io/baremetal-operator"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/metal3-io/metal3-docs/blob/main/design/baremetal-operator/bmc-events.md"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200", "CWE-653" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-03-17T21:26:14Z",
    "nvd_published_at" : "2025-03-17T22:15:14Z"
  }
}