cve.bz

CVE-2024-43803 metal3-io baremetal-operator

4.9 mediumEPSS 0.6%Fix available

Medium (4.9) in metal3-io baremetal-operator. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/metal3-io/baremetal-operator 0.5.2, 0.6.2, 0.8.0.

On this page
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.

Severity

CVSS 3.1

4.9 medium
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 48th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2024-09-03. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-653 Improper Isolation or Compartmentalization
OWASP Top 10
A01:2025 Broken Access Control, A06:2025 Insecure Design
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-43803 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-43803?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-43803?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-43803 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
metal3-io baremetal-operator>= 0.7.0, < 0.8.0
metal3-io baremetal-operator>= 0.6.0, < 0.6.2
metal3-io baremetal-operator< 0.5.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-pqfh-xh7w-7h3pGogithub.com/metal3-io/baremetal-operator>=0.7.0-rc.0 <0.8.00.8.0
GHSA-pqfh-xh7w-7h3pGogithub.com/metal3-io/baremetal-operator>=0.6.0 <0.6.20.6.2
GHSA-pqfh-xh7w-7h3pGogithub.com/metal3-io/baremetal-operator<0.5.20.5.2
GO-2024-3109Gogithub.com/metal3-io/baremetal-operator<0.5.2
>=0.6.0 <0.6.2
>=0.7.0-rc.0 <0.8.0
0.5.2, 0.6.2, 0.8.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
SUSELinux Enterprise Module for Package Hub 15 SP6govulncheck-vulndb0.0.20250108T191942-150000.1.26.1SUSE-SU-2025:0060-1
openSUSELeap 15.6govulncheck-vulndb0.0.20250108T191942-150000.1.26.1SUSE-SU-2025:0060-1
openSUSETumbleweedgovulncheck-vulndb0.0.20241220T214820-1.1openSUSE-SU-2024:14608-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This issue is considered moderate rather than important because it requires specific conditions to be exploited. The vulnerability relies on an attacker already having the ability to create or modify a BareMetalHost resource, which typically requires elevated permissions. Furthermore, the flaw only allows exfiltration of Secrets by referencing them in another namespace, but does not directly expose or escalate privileges across the cluster. It also doesn't impact the integrity or availability of the system but is limited to confidentiality concerns within a specific scope. Proper RBAC policies can mitigate this risk, reducing its overall severity.

Red Hat's mitigation

The Operator can configure BMO RBAC to be the namespace scoped for Secrets, instead of the cluster scoped to prevent BMO from accessing Secrets from other namespaces.

ProductPackageStateAdvisory
Red Hat OpenShift Container Platform 4.16openshift4/ose-baremetal-rhel9-operator:v4.16.0-202409121637.p0.gae55a70.assembly.stream.el9Fixed 2024-09-24RHSA-2024:6824
Red Hat OpenShift Container Platform 4.18openshift4/aws-kms-encryption-provider-rhel9:v4.18.0-202501230001.p0.g088dcaf.assembly.stream.el9Fixed 2025-02-25RHSA-2024:6122
Red Hat OpenShift Container Platform 4.18openshift4/azure-kms-encryption-provider-rhel9:v4.18.0-202501230001.p0.gd4fb1b6.assembly.stream.el9Fixed 2025-02-25RHSA-2024:6122
Red Hat OpenShift Container Platform 4.18openshift4/azure-service-rhel9-operator:v4.18.0-202501230001.p0.g11ced00.assembly.stream.el9Fixed 2025-02-25RHSA-2024:6122
Red Hat OpenShift Container Platform 4.18openshift4/cloud-network-config-controller-rhel9:v4.18.0-202501230001.p0.gf648c78.assembly.stream.el9Fixed 2025-02-25RHSA-2024:6122
Red Hat OpenShift Container Platform 4.18openshift4/container-networking-plugins-microshift-rhel9:v4.18.0-202501230001.p0.g24a6532.assembly.stream.el9Fixed 2025-02-25RHSA-2024:6122
Red Hat OpenShift Container Platform 4.18openshift4/driver-toolkit-rhel9:v4.18.0-202502100301.p0.g2e139ed.assembly.stream.el9Fixed 2025-02-25RHSA-2024:6122
Red Hat OpenShift Container Platform 4.18openshift4/egress-router-cni-rhel9:v4.18.0-202501230001.p0.g3193a75.assembly.stream.el9Fixed 2025-02-25RHSA-2024:6122
Red Hat OpenShift Container Platform 4.18openshift4/frr-rhel9:v4.18.0-202502041302.p0.g1ad8f2e.assembly.stream.el9Fixed 2025-02-25RHSA-2024:6122
Red Hat OpenShift Container Platform 4.18openshift4/insights-runtime-exporter-rhel9:v4.18.0-202501230001.p0.g7149f2d.assembly.stream.el9Fixed 2025-02-25RHSA-2024:6122
Red Hat OpenShift Container Platform 4.18openshift4/insights-runtime-extractor-rhel9:v4.18.0-202501230001.p0.g7149f2d.assembly.stream.el9Fixed 2025-02-25RHSA-2024:6122
Red Hat OpenShift Container Platform 4.18openshift4/kube-metrics-server-rhel9:v4.18.0-202501230001.p0.g962ccca.assembly.stream.el9Fixed 2025-02-25RHSA-2024:6122
Red Hat OpenShift Container Platform 4.18openshift4/kubevirt-csi-driver-rhel9:v4.18.0-202501230001.p0.gba2234b.assembly.stream.el9Fixed 2025-02-25RHSA-2024:6122
Red Hat OpenShift Container Platform 4.18openshift4/network-tools-rhel9:v4.18.0-202502111035.p0.gf76635f.assembly.stream.el9Fixed 2025-02-25RHSA-2024:6122
Red Hat OpenShift Container Platform 4.18openshift4/oc-mirror-plugin-rhel9:v4.18.0-202502100934.p0.gc00c7c9.assembly.stream.el9Fixed 2025-02-25RHSA-2024:6122
Red Hat OpenShift Container Platform 4.18openshift4/openshift-route-controller-manager-rhel9:v4.18.0-202501230001.p0.g07daee4.assembly.stream.el9Fixed 2025-02-25RHSA-2024:6122
Red Hat OpenShift Container Platform 4.18openshift4/ose-agent-installer-api-server-rhel9:v4.18.0-202502040032.p0.ge5a4005.assembly.stream.el9Fixed 2025-02-25RHSA-2024:6122
Red Hat OpenShift Container Platform 4.18openshift4/ose-agent-installer-csr-approver-rhel9:v4.18.0-202502040032.p0.g5348c85.assembly.stream.el9Fixed 2025-02-25RHSA-2024:6122
Red Hat OpenShift Container Platform 4.18openshift4/ose-agent-installer-node-agent-rhel9:v4.18.0-202502041302.p0.g51a74ac.assembly.stream.el9Fixed 2025-02-25RHSA-2024:6122
Red Hat OpenShift Container Platform 4.18openshift4/ose-agent-installer-orchestrator-rhel9:v4.18.0-202501230001.p0.g5348c85.assembly.stream.el9Fixed 2025-02-25RHSA-2024:6122
171 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2024-43803.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON