← Übersicht Nicht im beobachteten Stack

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

CVE-2024-43803 · GHSA-pqfh-xh7w-7h3p · GO-2024-3109

Mittel · CVSS 6.9 SUSE: moderateRed Hat: Moderate Netzwerk · mit Login Kein Fix bekannt

Veröffentlicht
03.09.2024 20:56
Zuletzt geändert
16.03.2026
EPSS (30 Tage)
0.6 %
CVSS-Vektor
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

Beschreibung

Originaltext der Quelle, nicht übersetzt.

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.

Status beim Hersteller

Red Hat stuft seine Produktlinien ein: 7 behoben, 1 nicht betroffen.

Red Hat OpenShift Container Platform 4.16 Behoben openshift4/ose-baremetal-rhel9-operator RHSA-2024:6824
Red Hat OpenShift Container Platform 4.18 Behoben openshift4/aws-kms-encryption-provider-rhel9, openshift4/azure-kms-encryption-provider-rhel9, openshift4/azure-service-rhel9-operator, openshift4/cloud-network-config-controller-rhel9, openshift4/container-networking-plugins-microshift-rhel9, openshift4/driver-toolkit-rhel9, openshift4/egress-router-cni-rhel9, openshift4/frr-rhel9, openshift4/insights-runtime-exporter-rhel9, openshift4/insights-runtime-extractor-rhel9, openshift4/kube-metrics-server-rhel9, openshift4/kubevirt-csi-driver-rhel9, openshift4/network-tools-rhel9, openshift4/oc-mirror-plugin-rhel9, openshift4/openshift-route-controller-manager-rhel9, openshift4/ose-agent-installer-api-server-rhel9, openshift4/ose-agent-installer-csr-approver-rhel9, openshift4/ose-agent-installer-node-agent-rhel9, openshift4/ose-agent-installer-orchestrator-rhel9, openshift4/ose-agent-installer-utils-rhel9, openshift4/ose-apiserver-network-proxy-rhel9, openshift4/ose-aws-cloud-controller-manager-rhel9, openshift4/ose-aws-cluster-api-controllers-rhel9, openshift4/ose-aws-ebs-csi-driver-rhel9, openshift4/ose-aws-ebs-csi-driver-rhel9-operator und 165 weitere RHSA-2024:6122
SUSE Linux Enterprise Server 16.0 Behoben govulncheck-vulndb-0.0.20250814T182633-160000.1.2
SUSE Linux Enterprise Server 16.1 Behoben govulncheck-vulndb-0.0.20260916T180043-160100.1.1
SUSE Linux Enterprise Server for SAP applications 16.0 Behoben govulncheck-vulndb-0.0.20250814T182633-160000.1.2
SUSE Linux Enterprise Server for SAP applications 16.1 Behoben govulncheck-vulndb-0.0.20260916T180043-160100.1.1
openSUSE Tumbleweed Behoben govulncheck-vulndb-0.0.20241220T214820-1.1
Nicht betroffen (1)
Red Hat OpenShift Container Platform 4.16Nicht betroffenverwundbarer Code nicht enthaltenopenshift4/driver-toolkit-rhel9, openshift4/network-tools-rhel9, openshift4/ose-agent-installer-api-server-rhel9, openshift4/ose-agent-installer-node-agent-rhel9, openshift4/ose-baremetal-installer-rhel9, openshift4/ose-cluster-image-registry-rhel9-operator, openshift4/ose-cluster-monitoring-rhel9-operator, openshift4/ose-cluster-network-rhel9-operator, openshift4/ose-cluster-node-tuning-rhel9-operator, openshift4/ose-console-rhel9, openshift4/ose-docker-builder-rhel9, openshift4/ose-hypershift-rhel9, openshift4/ose-installer-altinfra-rhel9, openshift4/ose-installer-artifacts-rhel9, openshift4/ose-installer-rhel9, openshift4/ose-ironic-agent-rhel9, openshift4/ose-ironic-machine-os-downloader-rhel9, openshift4/ose-ironic-rhel9, openshift4/ose-machine-config-rhel9-operator, openshift4/ose-machine-os-images-rhel9, openshift4/ose-openshift-controller-manager-rhel9, openshift4/ose-operator-framework-tools-rhel9, openshift4/ose-operator-lifecycle-manager-rhel9, openshift4/ose-operator-registry-rhel9, openshift4/ose-ovn-kubernetes-rhel9 und 6 weitere
Weitere betroffene Pakete (8)
CVEmetal3-io/baremetal-operatorkein Fix bekanntCVE-2024-43803
Gogithub.com/metal3-io/baremetal-operator0.6.0 → 0.6.2GHSA-pqfh-xh7w-7h3p
Gogithub.com/metal3-io/baremetal-operator0.5.2GHSA-pqfh-xh7w-7h3p
Gogithub.com/metal3-io/baremetal-operator0.7.0-rc.0 → 0.8.0GHSA-pqfh-xh7w-7h3p
Gogithub.com/metal3-io/baremetal-operator0.5.2, 0.6.0 → 0.6.2, 0.7.0-rc.0 → 0.8.0GO-2024-3109
SUSE:Linux Enterprise Module for Package Hub 15 SP6govulncheck-vulndb0.0.20250108T191942-150000.1.26.1SUSE-SU-2025:0060-1
openSUSE:Leap 15.6govulncheck-vulndb0.0.20250108T191942-150000.1.26.1SUSE-SU-2025:0060-1
openSUSE:Tumbleweedgovulncheck-vulndb0.0.20241220T214820-1.1openSUSE-SU-2024:14608-1

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · mit Login) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.