We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.

Please see our statement on Data Privacy.

Crisp.chat (Helpdesk and Chat)

Ok

THREATINT
PUBLISHED

CVE-2024-43803

BMO can expose particularly named secrets from other namespaces via BMH CRD



Description

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 versions of the baremetal-operator prior to 0.8.0, 0.6.2, and 0.5.2 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). 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. 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.7.0, v0.6.2 and v0.5.2 and users should upgrade to those versions. Prior upgrading, duplicate the BMC Secrets to the namespace where the corresponding BMH is. After upgrade, remove the old Secrets. As a workaround, an operator can configure BMO RBAC to be namespace scoped for Secrets, instead of cluster scoped, to prevent BMO from accessing Secrets from other namespaces.

Reserved 2024-08-16 | Published 2024-09-03 | Updated 2024-09-03 | Assigner GitHub_M


MEDIUM: 4.9CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Problem types

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

CWE-653: Improper Isolation or Compartmentalization

Product status

>= 0.7.0, < 0.8.0
affected

>= 0.6.0, < 0.6.2
affected

< 0.5.2
affected

References

github.com/...erator/security/advisories/GHSA-pqfh-xh7w-7h3p

github.com/metal3-io/baremetal-operator/pull/1929

github.com/metal3-io/baremetal-operator/pull/1930

github.com/metal3-io/baremetal-operator/pull/1931

github.com/...ommit/3af4882e9c5fadc1a7550f53daea21dccd271f74

github.com/...ommit/bedae7b997d16f36e772806681569bb8eb4dadbb

github.com/...ommit/c2b5a557641bc273367635124047d6c958aa15f7

cve.org (CVE-2024-43803)

nvd.nist.gov (CVE-2024-43803)

Download JSON

Share this page
https://cve.threatint.com/CVE/CVE-2024-43803

Support options

Helpdesk Chat, Email, Knowledgebase
Telegram Chat
Subscribe to our newsletter to learn more about our work.