CVE-2025-29781
Vulnerability from cvelistv5
Published
2025-03-17 21:37
Modified
2025-03-18 14:10
Severity ?
6.5 (Medium) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
EPSS score ?
0.01% (0.01584)
Summary
The Bare Metal Operator (BMO) implements a Kubernetes API for managing bare metal hosts in Metal3. Baremetal Operator enables users to load Secret from arbitrary namespaces upon deployment of the namespace scoped Custom Resource `BMCEventSubscription`. Prior to versions 0.8.1 and 0.9.1, an adversary Kubernetes account with only namespace level roles (e.g. a tenant controlling a namespace) may create a `BMCEventSubscription` in his authorized namespace and then load Secrets from his unauthorized namespaces to his authorized namespace via the Baremetal Operator, causing Secret Leakage. The patch makes BMO refuse to read Secrets from other namespace than where the corresponding BMH resource is. The patch does not change the `BMCEventSubscription` API in BMO, but stricter validation will fail the request at admission time. It will also prevent the controller reading such Secrets, in case the BMCES CR has already been deployed. The issue exists for all versions of BMO, and is patched in BMO releases v0.9.1 and v0.8.1. Prior upgrading to patched BMO version, duplicate any existing Secret pointed to by `BMCEventSubscription`'s `httpHeadersRef` to the same namespace where the corresponding BMH exists. After upgrade, remove the old Secrets. As a workaround, the operator can configure BMO RBAC to be namespace scoped, instead of cluster scoped, to prevent BMO from accessing Secrets from other namespaces, and/or use `WATCH_NAMESPACE` configuration option to limit BMO to single namespace.
References
security-advisories@github.comhttps://github.com/metal3-io/baremetal-operator/commit/19f8443b1fe182f76dd81b43122e8dd102f8b94c
security-advisories@github.comhttps://github.com/metal3-io/baremetal-operator/pull/2321
security-advisories@github.comhttps://github.com/metal3-io/baremetal-operator/pull/2322
security-advisories@github.comhttps://github.com/metal3-io/baremetal-operator/security/advisories/GHSA-c98h-7hp9-v9hq
security-advisories@github.comhttps://github.com/metal3-io/metal3-docs/blob/main/design/baremetal-operator/bmc-events.md
134c704f-9b21-4f2e-91b3-4a467353bcc0https://github.com/metal3-io/metal3-docs/blob/main/design/baremetal-operator/bmc-events.md
Impacted products
Vendor Product Version
metal3-io baremetal-operator Version: = 0.9.0
Version: < 0.8.1
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
   containers: {
      adp: [
         {
            metrics: [
               {
                  other: {
                     content: {
                        id: "CVE-2025-29781",
                        options: [
                           {
                              Exploitation: "poc",
                           },
                           {
                              Automatable: "no",
                           },
                           {
                              "Technical Impact": "partial",
                           },
                        ],
                        role: "CISA Coordinator",
                        timestamp: "2025-03-18T14:09:58.967344Z",
                        version: "2.0.3",
                     },
                     type: "ssvc",
                  },
               },
            ],
            providerMetadata: {
               dateUpdated: "2025-03-18T14:10:03.696Z",
               orgId: "134c704f-9b21-4f2e-91b3-4a467353bcc0",
               shortName: "CISA-ADP",
            },
            references: [
               {
                  tags: [
                     "exploit",
                  ],
                  url: "https://github.com/metal3-io/metal3-docs/blob/main/design/baremetal-operator/bmc-events.md",
               },
            ],
            title: "CISA ADP Vulnrichment",
         },
      ],
      cna: {
         affected: [
            {
               product: "baremetal-operator",
               vendor: "metal3-io",
               versions: [
                  {
                     status: "affected",
                     version: "= 0.9.0",
                  },
                  {
                     status: "affected",
                     version: "< 0.8.1",
                  },
               ],
            },
         ],
         descriptions: [
            {
               lang: "en",
               value: "The Bare Metal Operator (BMO) implements a Kubernetes API for managing bare metal hosts in Metal3. Baremetal Operator enables users to load Secret from arbitrary namespaces upon deployment of the namespace scoped Custom Resource `BMCEventSubscription`. Prior to versions 0.8.1 and 0.9.1, an adversary Kubernetes account with only namespace level roles (e.g. a tenant controlling a namespace) may create a `BMCEventSubscription` in his authorized namespace and then load Secrets from his unauthorized namespaces to his authorized namespace via the Baremetal Operator, causing Secret Leakage. The patch makes BMO refuse to read Secrets from other namespace than where the corresponding BMH resource is. The patch does not change the `BMCEventSubscription` API in BMO, but stricter validation will fail the request at admission time. It will also prevent the controller reading such Secrets, in case the BMCES CR has already been deployed. The issue exists for all versions of BMO, and is patched in BMO releases v0.9.1 and v0.8.1. Prior upgrading to patched BMO version, duplicate any existing Secret pointed to by `BMCEventSubscription`'s `httpHeadersRef` to the same namespace where the corresponding BMH exists. After upgrade, remove the old Secrets. As a workaround, the operator can configure BMO RBAC to be namespace scoped, instead of cluster scoped, to prevent BMO from accessing Secrets from other namespaces, and/or use `WATCH_NAMESPACE` configuration option to limit BMO to single namespace.",
            },
         ],
         metrics: [
            {
               cvssV3_1: {
                  attackComplexity: "LOW",
                  attackVector: "LOCAL",
                  availabilityImpact: "NONE",
                  baseScore: 6.5,
                  baseSeverity: "MEDIUM",
                  confidentialityImpact: "HIGH",
                  integrityImpact: "NONE",
                  privilegesRequired: "LOW",
                  scope: "CHANGED",
                  userInteraction: "NONE",
                  vectorString: "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N",
                  version: "3.1",
               },
            },
         ],
         problemTypes: [
            {
               descriptions: [
                  {
                     cweId: "CWE-200",
                     description: "CWE-200: Exposure of Sensitive Information to an Unauthorized Actor",
                     lang: "en",
                     type: "CWE",
                  },
               ],
            },
            {
               descriptions: [
                  {
                     cweId: "CWE-653",
                     description: "CWE-653: Improper Isolation or Compartmentalization",
                     lang: "en",
                     type: "CWE",
                  },
               ],
            },
         ],
         providerMetadata: {
            dateUpdated: "2025-03-17T21:37:31.856Z",
            orgId: "a0819718-46f1-4df5-94e2-005712e83aaa",
            shortName: "GitHub_M",
         },
         references: [
            {
               name: "https://github.com/metal3-io/baremetal-operator/security/advisories/GHSA-c98h-7hp9-v9hq",
               tags: [
                  "x_refsource_CONFIRM",
               ],
               url: "https://github.com/metal3-io/baremetal-operator/security/advisories/GHSA-c98h-7hp9-v9hq",
            },
            {
               name: "https://github.com/metal3-io/baremetal-operator/pull/2321",
               tags: [
                  "x_refsource_MISC",
               ],
               url: "https://github.com/metal3-io/baremetal-operator/pull/2321",
            },
            {
               name: "https://github.com/metal3-io/baremetal-operator/pull/2322",
               tags: [
                  "x_refsource_MISC",
               ],
               url: "https://github.com/metal3-io/baremetal-operator/pull/2322",
            },
            {
               name: "https://github.com/metal3-io/baremetal-operator/commit/19f8443b1fe182f76dd81b43122e8dd102f8b94c",
               tags: [
                  "x_refsource_MISC",
               ],
               url: "https://github.com/metal3-io/baremetal-operator/commit/19f8443b1fe182f76dd81b43122e8dd102f8b94c",
            },
            {
               name: "https://github.com/metal3-io/metal3-docs/blob/main/design/baremetal-operator/bmc-events.md",
               tags: [
                  "x_refsource_MISC",
               ],
               url: "https://github.com/metal3-io/metal3-docs/blob/main/design/baremetal-operator/bmc-events.md",
            },
         ],
         source: {
            advisory: "GHSA-c98h-7hp9-v9hq",
            discovery: "UNKNOWN",
         },
         title: "Bare Metal Operator (BMO) can expose any secret from other namespaces via BMCEventSubscription CRD",
      },
   },
   cveMetadata: {
      assignerOrgId: "a0819718-46f1-4df5-94e2-005712e83aaa",
      assignerShortName: "GitHub_M",
      cveId: "CVE-2025-29781",
      datePublished: "2025-03-17T21:37:31.856Z",
      dateReserved: "2025-03-11T14:23:00.475Z",
      dateUpdated: "2025-03-18T14:10:03.696Z",
      state: "PUBLISHED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.1",
   "vulnerability-lookup:meta": {
      nvd: "{\"cve\":{\"id\":\"CVE-2025-29781\",\"sourceIdentifier\":\"security-advisories@github.com\",\"published\":\"2025-03-17T22:15:14.493\",\"lastModified\":\"2025-03-18T15:16:00.747\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"The Bare Metal Operator (BMO) implements a Kubernetes API for managing bare metal hosts in Metal3. Baremetal Operator enables users to load Secret from arbitrary namespaces upon deployment of the namespace scoped Custom Resource `BMCEventSubscription`. Prior to versions 0.8.1 and 0.9.1, an adversary Kubernetes account with only namespace level roles (e.g. a tenant controlling a namespace) may create a `BMCEventSubscription` in his authorized namespace and then load Secrets from his unauthorized namespaces to his authorized namespace via the Baremetal Operator, causing Secret Leakage. The patch makes BMO refuse to read Secrets from other namespace than where the corresponding BMH resource is. The patch does not change the `BMCEventSubscription` API in BMO, but stricter validation will fail the request at admission time. It will also prevent the controller reading such Secrets, in case the BMCES CR has already been deployed. The issue exists for all versions of BMO, and is patched in BMO releases v0.9.1 and v0.8.1. Prior upgrading to patched BMO version, duplicate any existing Secret pointed to by `BMCEventSubscription`'s `httpHeadersRef` to the same namespace where the corresponding BMH exists. After upgrade, remove the old Secrets. As a workaround, the operator can configure BMO RBAC to be namespace scoped, instead of cluster scoped, to prevent BMO from accessing Secrets from other namespaces, and/or use `WATCH_NAMESPACE` configuration option to limit BMO to single namespace.\"},{\"lang\":\"es\",\"value\":\"Bare Metal Operator (BMO) implementa una API de Kubernetes para administrar hosts de hardware en Metal3. Este operador permite a los usuarios cargar secretos desde espacios de nombres arbitrarios al implementar el recurso personalizado `BMCEventSubscription` con ámbito de espacio de nombres. Antes de las versiones 0.8.1 y 0.9.1, una cuenta de Kubernetes adversaria con roles solo a nivel de espacio de nombres (por ejemplo, un inquilino que controla un espacio de nombres) podía crear una `BMCEventSubscription` en su espacio de nombres autorizado y luego cargar secretos desde sus espacios de nombres no autorizados a su espacio de nombres autorizado mediante el Baremetal Operator, lo que causaba una fuga de secretos. El parche hace que BMO se niegue a leer secretos de un espacio de nombres diferente al del recurso BMH correspondiente. El parche no modifica la API `BMCEventSubscription` en BMO, pero una validación más estricta fallará la solicitud en el momento de la admisión. También impedirá que el controlador lea dichos secretos, en caso de que el BMCES CR ya se haya implementado. El problema existe en todas las versiones de BMO y está corregido en las versiones 0.9.1 y 0.8.1 de BMO. Antes de actualizar a la versión corregida de BMO, duplique cualquier secreto existente al que apunte `httpHeadersRef` de `BMCEventSubscription` en el mismo espacio de nombres donde exista el BMH correspondiente. Tras la actualización, elimine los secretos antiguos. Como workaround, el operador puede configurar el RBAC de BMO para que tenga alcance de espacio de nombres, en lugar de clúster, para evitar que BMO acceda a secretos de otros espacios de nombres, o bien usar la opción de configuración `WATCH_NAMESPACE` para limitar BMO a un solo espacio de nombres.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N\",\"baseScore\":6.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"CHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"NONE\"},\"exploitabilityScore\":2.0,\"impactScore\":4.0}]},\"weaknesses\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-200\"},{\"lang\":\"en\",\"value\":\"CWE-653\"}]}],\"references\":[{\"url\":\"https://github.com/metal3-io/baremetal-operator/commit/19f8443b1fe182f76dd81b43122e8dd102f8b94c\",\"source\":\"security-advisories@github.com\"},{\"url\":\"https://github.com/metal3-io/baremetal-operator/pull/2321\",\"source\":\"security-advisories@github.com\"},{\"url\":\"https://github.com/metal3-io/baremetal-operator/pull/2322\",\"source\":\"security-advisories@github.com\"},{\"url\":\"https://github.com/metal3-io/baremetal-operator/security/advisories/GHSA-c98h-7hp9-v9hq\",\"source\":\"security-advisories@github.com\"},{\"url\":\"https://github.com/metal3-io/metal3-docs/blob/main/design/baremetal-operator/bmc-events.md\",\"source\":\"security-advisories@github.com\"},{\"url\":\"https://github.com/metal3-io/metal3-docs/blob/main/design/baremetal-operator/bmc-events.md\",\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\"}]}}",
      vulnrichment: {
         containers: "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2025-29781\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"poc\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2025-03-18T14:09:58.967344Z\"}}}], \"references\": [{\"url\": \"https://github.com/metal3-io/metal3-docs/blob/main/design/baremetal-operator/bmc-events.md\", \"tags\": [\"exploit\"]}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2025-03-18T14:09:54.213Z\"}}], \"cna\": {\"title\": \"Bare Metal Operator (BMO) can expose any secret from other namespaces via BMCEventSubscription CRD\", \"source\": {\"advisory\": \"GHSA-c98h-7hp9-v9hq\", \"discovery\": \"UNKNOWN\"}, \"metrics\": [{\"cvssV3_1\": {\"scope\": \"CHANGED\", \"version\": \"3.1\", \"baseScore\": 6.5, \"attackVector\": \"LOCAL\", \"baseSeverity\": \"MEDIUM\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N\", \"integrityImpact\": \"NONE\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"availabilityImpact\": \"NONE\", \"privilegesRequired\": \"LOW\", \"confidentialityImpact\": \"HIGH\"}}], \"affected\": [{\"vendor\": \"metal3-io\", \"product\": \"baremetal-operator\", \"versions\": [{\"status\": \"affected\", \"version\": \"= 0.9.0\"}, {\"status\": \"affected\", \"version\": \"< 0.8.1\"}]}], \"references\": [{\"url\": \"https://github.com/metal3-io/baremetal-operator/security/advisories/GHSA-c98h-7hp9-v9hq\", \"name\": \"https://github.com/metal3-io/baremetal-operator/security/advisories/GHSA-c98h-7hp9-v9hq\", \"tags\": [\"x_refsource_CONFIRM\"]}, {\"url\": \"https://github.com/metal3-io/baremetal-operator/pull/2321\", \"name\": \"https://github.com/metal3-io/baremetal-operator/pull/2321\", \"tags\": [\"x_refsource_MISC\"]}, {\"url\": \"https://github.com/metal3-io/baremetal-operator/pull/2322\", \"name\": \"https://github.com/metal3-io/baremetal-operator/pull/2322\", \"tags\": [\"x_refsource_MISC\"]}, {\"url\": \"https://github.com/metal3-io/baremetal-operator/commit/19f8443b1fe182f76dd81b43122e8dd102f8b94c\", \"name\": \"https://github.com/metal3-io/baremetal-operator/commit/19f8443b1fe182f76dd81b43122e8dd102f8b94c\", \"tags\": [\"x_refsource_MISC\"]}, {\"url\": \"https://github.com/metal3-io/metal3-docs/blob/main/design/baremetal-operator/bmc-events.md\", \"name\": \"https://github.com/metal3-io/metal3-docs/blob/main/design/baremetal-operator/bmc-events.md\", \"tags\": [\"x_refsource_MISC\"]}], \"descriptions\": [{\"lang\": \"en\", \"value\": \"The Bare Metal Operator (BMO) implements a Kubernetes API for managing bare metal hosts in Metal3. Baremetal Operator enables users to load Secret from arbitrary namespaces upon deployment of the namespace scoped Custom Resource `BMCEventSubscription`. Prior to versions 0.8.1 and 0.9.1, an adversary Kubernetes account with only namespace level roles (e.g. a tenant controlling a namespace) may create a `BMCEventSubscription` in his authorized namespace and then load Secrets from his unauthorized namespaces to his authorized namespace via the Baremetal Operator, causing Secret Leakage. The patch makes BMO refuse to read Secrets from other namespace than where the corresponding BMH resource is. The patch does not change the `BMCEventSubscription` API in BMO, but stricter validation will fail the request at admission time. It will also prevent the controller reading such Secrets, in case the BMCES CR has already been deployed. The issue exists for all versions of BMO, and is patched in BMO releases v0.9.1 and v0.8.1. Prior upgrading to patched BMO version, duplicate any existing Secret pointed to by `BMCEventSubscription`'s `httpHeadersRef` to the same namespace where the corresponding BMH exists. After upgrade, remove the old Secrets. As a workaround, the operator can configure BMO RBAC to be namespace scoped, instead of cluster scoped, to prevent BMO from accessing Secrets from other namespaces, and/or use `WATCH_NAMESPACE` configuration option to limit BMO to single namespace.\"}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-200\", \"description\": \"CWE-200: Exposure of Sensitive Information to an Unauthorized Actor\"}]}, {\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-653\", \"description\": \"CWE-653: Improper Isolation or Compartmentalization\"}]}], \"providerMetadata\": {\"orgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"shortName\": \"GitHub_M\", \"dateUpdated\": \"2025-03-17T21:37:31.856Z\"}}}",
         cveMetadata: "{\"cveId\": \"CVE-2025-29781\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2025-03-18T14:10:03.696Z\", \"dateReserved\": \"2025-03-11T14:23:00.475Z\", \"assignerOrgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"datePublished\": \"2025-03-17T21:37:31.856Z\", \"assignerShortName\": \"GitHub_M\"}",
         dataType: "CVE_RECORD",
         dataVersion: "5.1",
      },
   },
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.