gsd-2024-3177
Vulnerability from gsd
Modified
2024-04-03 05:02
Details
A security issue was discovered in Kubernetes where users may be able to launch containers that bypass the mountable secrets policy enforced by the ServiceAccount admission plugin when using containers, init containers, and ephemeral containers with the envFrom field populated. The policy ensures pods running with a service account may only reference secrets specified in the service account’s secrets field. Kubernetes clusters are only affected if the ServiceAccount admission plugin and the kubernetes.io/enforce-mountable-secrets annotation are used together with containers, init containers, and ephemeral containers with the envFrom field populated.
Aliases


To clipboard 

{
   gsd: {
      metadata: {
         exploitCode: "unknown",
         remediation: "unknown",
         reportConfidence: "confirmed",
         type: "vulnerability",
      },
      osvSchema: {
         aliases: [
            "CVE-2024-3177",
         ],
         details: "A security issue was discovered in Kubernetes where users may be able to launch containers that bypass the mountable secrets policy enforced by the ServiceAccount admission plugin when using containers, init containers, and ephemeral containers with the envFrom field populated. The policy ensures pods running with a service account may only reference secrets specified in the service account’s secrets field. Kubernetes clusters are only affected if the ServiceAccount admission plugin and the kubernetes.io/enforce-mountable-secrets annotation are used together with containers, init containers, and ephemeral containers with the envFrom field populated.\n\n",
         id: "GSD-2024-3177",
         modified: "2024-04-03T05:02:29.897756Z",
         schema_version: "1.4.0",
      },
   },
   namespaces: {
      "cve.org": {
         CVE_data_meta: {
            ASSIGNER: "security@kubernetes.io",
            ID: "CVE-2024-3177",
            STATE: "PUBLIC",
         },
         affects: {
            vendor: {
               vendor_data: [
                  {
                     product: {
                        product_data: [
                           {
                              product_name: "Kubernetes",
                              version: {
                                 version_data: [
                                    {
                                       version_affected: "<=",
                                       version_name: "v1.27.12",
                                       version_value: "<=",
                                    },
                                    {
                                       version_affected: "=",
                                       version_value: "v1.28.0 - v1.28.8",
                                    },
                                    {
                                       version_affected: "=",
                                       version_value: "v1.29.0 - v1.29.3",
                                    },
                                 ],
                              },
                           },
                        ],
                     },
                     vendor_name: "Kubernetes",
                  },
               ],
            },
         },
         credits: [
            {
               lang: "en",
               value: "tha3e1vl",
            },
         ],
         data_format: "MITRE",
         data_type: "CVE",
         data_version: "4.0",
         description: {
            description_data: [
               {
                  lang: "eng",
                  value: "A security issue was discovered in Kubernetes where users may be able to launch containers that bypass the mountable secrets policy enforced by the ServiceAccount admission plugin when using containers, init containers, and ephemeral containers with the envFrom field populated. The policy ensures pods running with a service account may only reference secrets specified in the service account’s secrets field. Kubernetes clusters are only affected if the ServiceAccount admission plugin and the kubernetes.io/enforce-mountable-secrets annotation are used together with containers, init containers, and ephemeral containers with the envFrom field populated.\n\n",
               },
            ],
         },
         generator: {
            engine: "Vulnogram 0.1.0-dev",
         },
         impact: {
            cvss: [
               {
                  attackComplexity: "LOW",
                  attackVector: "NETWORK",
                  availabilityImpact: "NONE",
                  baseScore: 2.7,
                  baseSeverity: "LOW",
                  confidentialityImpact: "LOW",
                  integrityImpact: "NONE",
                  privilegesRequired: "HIGH",
                  scope: "UNCHANGED",
                  userInteraction: "NONE",
                  vectorString: "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N",
                  version: "3.1",
               },
            ],
         },
         problemtype: {
            problemtype_data: [
               {
                  description: [
                     {
                        cweId: "CWE-20",
                        lang: "eng",
                        value: "CWE-20 Improper Input Validation",
                     },
                  ],
               },
            ],
         },
         references: {
            reference_data: [
               {
                  name: "https://groups.google.com/g/kubernetes-security-announce/c/JxjHf7fkVd8/m/oVCzypyOAQAJ",
                  refsource: "MISC",
                  url: "https://groups.google.com/g/kubernetes-security-announce/c/JxjHf7fkVd8/m/oVCzypyOAQAJ",
               },
               {
                  name: "https://github.com/kubernetes/kubernetes/issues/124336",
                  refsource: "MISC",
                  url: "https://github.com/kubernetes/kubernetes/issues/124336",
               },
               {
                  name: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WL54MTLGMTBZZO5PYGEGEBERTMADC4WC/",
                  refsource: "MISC",
                  url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WL54MTLGMTBZZO5PYGEGEBERTMADC4WC/",
               },
               {
                  name: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QRYFHIQ6XRKRYBI2F5UESH67BJBQXUPT/",
                  refsource: "MISC",
                  url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QRYFHIQ6XRKRYBI2F5UESH67BJBQXUPT/",
               },
            ],
         },
         solution: [
            {
               lang: "en",
               supportingMedia: [
                  {
                     base64: false,
                     type: "text/html",
                     value: "<div><div>To mitigate this vulnerability, upgrade Kubernetes: <a target=\"_blank\" rel=\"nofollow\" href=\"https://kubernetes.io/docs/tasks/administer-cluster/cluster-upgrade/\">https://kubernetes.io/docs/tasks/administer-cluster/cluster-upgrade/</a></div></div>",
                  },
               ],
               value: "To mitigate this vulnerability, upgrade Kubernetes:  https://kubernetes.io/docs/tasks/administer-cluster/cluster-upgrade/ \n\n\n\n",
            },
         ],
         source: {
            discovery: "INTERNAL",
         },
      },
      "nvd.nist.gov": {
         cve: {
            descriptions: [
               {
                  lang: "en",
                  value: "A security issue was discovered in Kubernetes where users may be able to launch containers that bypass the mountable secrets policy enforced by the ServiceAccount admission plugin when using containers, init containers, and ephemeral containers with the envFrom field populated. The policy ensures pods running with a service account may only reference secrets specified in the service account’s secrets field. Kubernetes clusters are only affected if the ServiceAccount admission plugin and the kubernetes.io/enforce-mountable-secrets annotation are used together with containers, init containers, and ephemeral containers with the envFrom field populated.\n\n",
               },
               {
                  lang: "es",
                  value: "Se descubrió un problema de seguridad en Kubernetes donde los usuarios pueden lanzar contenedores que omiten la política de secretos montables aplicada por el complemento de admisión ServiceAccount cuando usan contenedores, contenedores init y contenedores efímeros con el campo envFrom completo. La política garantiza que los pods que se ejecutan con una cuenta de servicio solo puedan hacer referencia a secretos especificados en el campo de secretos de la cuenta de servicio. Los clústeres de Kubernetes solo se ven afectados si el complemento de admisión ServiceAccount y la anotación kubernetes.io/enforce-mountable-secrets se usan junto con contenedores, contenedores init y contenedores efímeros con el campo envFrom completo.",
               },
            ],
            id: "CVE-2024-3177",
            lastModified: "2024-04-25T06:16:00.237",
            metrics: {
               cvssMetricV31: [
                  {
                     cvssData: {
                        attackComplexity: "LOW",
                        attackVector: "NETWORK",
                        availabilityImpact: "NONE",
                        baseScore: 2.7,
                        baseSeverity: "LOW",
                        confidentialityImpact: "LOW",
                        integrityImpact: "NONE",
                        privilegesRequired: "HIGH",
                        scope: "UNCHANGED",
                        userInteraction: "NONE",
                        vectorString: "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N",
                        version: "3.1",
                     },
                     exploitabilityScore: 1.2,
                     impactScore: 1.4,
                     source: "jordan@liggitt.net",
                     type: "Secondary",
                  },
               ],
            },
            published: "2024-04-22T23:15:51.180",
            references: [
               {
                  source: "jordan@liggitt.net",
                  url: "https://github.com/kubernetes/kubernetes/issues/124336",
               },
               {
                  source: "jordan@liggitt.net",
                  url: "https://groups.google.com/g/kubernetes-security-announce/c/JxjHf7fkVd8/m/oVCzypyOAQAJ",
               },
               {
                  source: "jordan@liggitt.net",
                  url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QRYFHIQ6XRKRYBI2F5UESH67BJBQXUPT/",
               },
               {
                  source: "jordan@liggitt.net",
                  url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WL54MTLGMTBZZO5PYGEGEBERTMADC4WC/",
               },
            ],
            sourceIdentifier: "jordan@liggitt.net",
            vulnStatus: "Awaiting Analysis",
            weaknesses: [
               {
                  description: [
                     {
                        lang: "en",
                        value: "CWE-20",
                     },
                  ],
                  source: "jordan@liggitt.net",
                  type: "Secondary",
               },
            ],
         },
      },
   },
}


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.