CVE-2024-43803

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.

• CWE-200
• CWE-653

• https://github.com/metal3-io/baremetal-operator/commit/3af4882e9c5fadc1a7550f53daea21dccd271f74
• https://github.com/metal3-io/baremetal-operator/commit/bedae7b997d16f36e772806681569bb8eb4dadbb
• https://github.com/metal3-io/baremetal-operator/commit/c2b5a557641bc273367635124047d6c958aa15f7
• 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
• https://github.com/metal3-io/baremetal-operator/security/advisories/GHSA-pqfh-xh7w-7h3p

Published

Sep 3, 2024

Last Modified

Jun 17, 2026

Status

Deferred

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2024-43797audiobookshelf is a self-hosted audiobook and podcast server…4.3
• CVE-2024-43798Chisel is a fast TCP/UDP tunnel, transported over HTTP, secu…8.6
• CVE-2024-43799Send is a library for streaming files from the file system a…4.7
• CVE-2024-43800serve-static serves static files. serve-static passes untrus…4.7
• CVE-2024-43801Jellyfin is an open source self hosted media server. The Jel…5.4
• CVE-2024-43802Vim is an improved version of the unix vi text editor. When …4.5
• CVE-2024-43804Roxy-WI is a web interface for managing Haproxy, Nginx, Apac…8.8
• CVE-2024-43805jupyterlab is an extensible environment for interactive and …6.1
• CVE-2024-43806Rustix is a set of safe Rust bindings to POSIX-ish APIs. Whe…6.5
• CVE-2024-43807In JetBrains TeamCity before 2024.07.1 multiple stored XSS w…5.4
• CVE-2024-43808In JetBrains TeamCity before 2024.07.1 self XSS was possible…5.4
• CVE-2024-43809In JetBrains TeamCity before 2024.07.1 reflected XSS was pos…6.1