CVE-2024-43803: Github.com/metal3 io/baremetal operator The Bare Metal Operator (BMO) Vulnerability

MODERATE
Advisory Identifier: GHSA-pqfh-xh7w-7h3p
CVSS 4.9
CWE-200 CWE-653
Published
Advisory Summary

CVE-2024-43803 is a MODERATE (CVSS 4.9) the bare metal operator (bmo) vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Github.com/metal3 io/baremetal operator libraries in the Go ecosystem. The issue involves the bare metal operator (bmo) can expose particularly named secrets from other namespaces via bmh crd. Remediation is available by upgrading affected packages to version 0.8.0, 0.6.2, 0.5.2.

CVE-2024-43803 at a Glance

CVE Identifier CVE-2024-43803
GHSA Identifier GHSA-pqfh-xh7w-7h3p
Severity MODERATE
CVSS v3.1 Base Score 4.9
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product Github.com/metal3 io/baremetal operator
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 4.9

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

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

How to Fix CVE-2024-43803

To remediate this vulnerability, upgrade all affected Github.com/metal3 io/baremetal operator 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 fixed: 0.8.0
Upgrade github.com/metal3-io/baremetal-operator to 0.8.0
github.com/metal3-io/baremetal-operator fixed: 0.6.2
Upgrade github.com/metal3-io/baremetal-operator to 0.6.2
github.com/metal3-io/baremetal-operator fixed: 0.5.2
Upgrade github.com/metal3-io/baremetal-operator to 0.5.2
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

How to Check if You Are Affected

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

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

Analyze the terminal output to locate any version of Github.com/metal3 io/baremetal operator in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.8.0), 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, 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. The `BareMetalHost` (BMH) CRD allows the `userData`, `metaData`, and `networkData` for the provisioned host to be specified as links to Kubernetes Secrets. There are fields for both the `Name` and `Namespace` of the Secret, meaning that the baremetal-operator will read a `Secret` from any namespace. A user with access to create or edit a `BareMetalHost` can thus exfiltrate a `Secret` from another namespace by using it as e.g. the `userData` for provisioning some host (note that this need not be a real host, it could be a VM somewhere). ### Limiting factors BMO will only read a key with the name `value` (or `userData`, `metaData`, or `networkData`), so that limits the exposure somewhat. `value` is probably a pretty common key though. Secrets used by _other_ `BareMetalHost`s in different namespaces are always vulnerable. It is probably relatively unusual for anyone other than cluster administrators to have RBAC access to create/edit a `BareMetalHost`. This vulnerability is only meaningful, if the cluster has users other than administrators and users' privileges are limited to their respective namespaces. ### Patches The patch prevents BMO from accepting links to Secrets from other namespaces as BMH input. Any BMH configuration is only read from the same namespace only. The problem is patched in BMO releases v0.8.0, v0.6.2 and v0.5.2 and users should upgrade to those versions. Prior upgrading and if needed, duplicate the BMC Secrets to the namespace where the corresponding BMH is. After upgrade, remove the old Secrets. ### Workarounds Operator can configure BMO RBAC to be namespace scoped for Secrets, instead of cluster scoped, to prevent BMO from accessing Secrets from other namespaces. ### References - https://nvd.nist.gov/vuln/detail/CVE-2024-43803 - https://github.com/metal3-io/baremetal-operator/pull/1929 - https://github.com/metal3-io/baremetal-operator/pull/1930 - https://github.com/metal3-io/baremetal-operator/pull/1931

CVE-2024-43803 Affected Github.com/metal3 io/baremetal operator Versions

3 component(s)
Fixed Versions:
0.8.00.6.20.5.2
Product / Package Ecosystem Affected Versions Fixed Version
github.com/metal3-io/baremetal-operator
Go
≥ 0.7.0-rc.0
< 0.8.0
0.8.0
github.com/metal3-io/baremetal-operator
Go
≥ 0.6.0
< 0.6.2
0.6.2
github.com/metal3-io/baremetal-operator
Go
< 0.5.2
0.5.2

References

Frequently Asked Questions

What is CVE-2024-43803?
CVE-2024-43803 is a security vulnerability in Github.com/metal3 io/baremetal operator involving The Bare Metal Operator (BMO) can expose particularly named secrets from other namespaces via BMH CRD under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which Github.com/metal3 io/baremetal operator versions are affected?
Affected versions include releases prior to 0.8.0, 0.6.2, 0.5.2 across affected packages: github.com/metal3-io/baremetal-operator.
What version fixes CVE-2024-43803?
Upgrading to 0.8.0, 0.6.2, 0.5.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/metal3-io/baremetal-operator affected?
Yes, github.com/metal3-io/baremetal-operator is affected in releases prior to 0.8.0, 0.6.2, 0.5.2. Upgrade your dependency to 0.8.0, 0.6.2, 0.5.2 or later.
What is the CVSS score of CVE-2024-43803?
CVE-2024-43803 has a CVSS v3.1 base score of 4.9 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2024-43803?
CVE-2024-43803 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-2024-43803?
Run the dependency tree command: 'inspect dependencies for github.com/metal3-io/baremetal-operator'. 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-pqfh-xh7w-7h3p",
  "modified" : "2024-09-03T21:45:28Z",
  "published" : "2024-09-03T20:13:25Z",
  "aliases" : [ "CVE-2024-43803" ],
  "summary" : "The Bare Metal Operator (BMO) can expose particularly named secrets from other namespaces via BMH CRD",
  "details" : "### Impact\nThe Bare Metal Operator (BMO) implements a Kubernetes API for managing bare metal hosts in Metal3. The `BareMetalHost` (BMH) CRD allows the `userData`, `metaData`, and `networkData` for the provisioned host to be specified as links to Kubernetes Secrets. There are fields for both the `Name` and `Namespace` of the Secret, meaning that the baremetal-operator will read a `Secret` from any namespace. A user with access to create or edit a `BareMetalHost` can thus exfiltrate a `Secret` from another namespace by using it as e.g. the `userData` for provisioning some host (note that this need not be a real host, it could be a VM somewhere).\n\n### Limiting factors\nBMO will only read a key with the name `value` (or `userData`, `metaData`, or `networkData`), so that limits the exposure somewhat. `value` is probably a pretty common key though. Secrets used by _other_ `BareMetalHost`s in different namespaces are always vulnerable.\n\nIt is probably relatively unusual for anyone other than cluster administrators to have RBAC access to create/edit a `BareMetalHost`. This vulnerability is only meaningful, if the cluster has users other than administrators and users' privileges are limited to their respective namespaces.\n\n### Patches\nThe patch prevents BMO from accepting links to Secrets from other namespaces as BMH input. Any BMH configuration is only read from the same namespace only.\n\nThe problem is patched in BMO releases v0.8.0, v0.6.2 and v0.5.2 and users should upgrade to those versions. Prior upgrading and if needed, duplicate the BMC Secrets to the namespace where the corresponding BMH is. After upgrade, remove the old Secrets.\n\n### Workarounds\nOperator can configure BMO RBAC to be namespace scoped for Secrets, instead of cluster scoped, to prevent BMO from accessing Secrets from other namespaces.\n\n### References\n- https://nvd.nist.gov/vuln/detail/CVE-2024-43803\n- https://github.com/metal3-io/baremetal-operator/pull/1929\n- https://github.com/metal3-io/baremetal-operator/pull/1930\n- https://github.com/metal3-io/baremetal-operator/pull/1931",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/metal3-io/baremetal-operator"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.7.0-rc.0"
      }, {
        "fixed" : "0.8.0"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/metal3-io/baremetal-operator"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.6.0"
      }, {
        "fixed" : "0.6.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/metal3-io/baremetal-operator"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.5.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/metal3-io/baremetal-operator/security/advisories/GHSA-pqfh-xh7w-7h3p"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-43803"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/metal3-io/baremetal-operator/pull/1929"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/metal3-io/baremetal-operator/pull/1930"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/metal3-io/baremetal-operator/pull/1931"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/metal3-io/baremetal-operator/commit/3af4882e9c5fadc1a7550f53daea21dccd271f74"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/metal3-io/baremetal-operator/commit/bedae7b997d16f36e772806681569bb8eb4dadbb"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/metal3-io/baremetal-operator/commit/c2b5a557641bc273367635124047d6c958aa15f7"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/metal3-io/baremetal-operator"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200", "CWE-653" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-09-03T20:13:25Z",
    "nvd_published_at" : "2024-09-03T19:15:14Z"
  }
}