fkie_cve-2024-7598
Vulnerability from fkie_nvd
Published
2025-03-20 17:15
Modified
2025-03-20 21:15
Summary
A security issue was discovered in Kubernetes where a malicious or compromised pod could bypass network restrictions enforced by network policies during namespace deletion. The order in which objects are deleted during namespace termination is not defined, and it is possible for network policies to be deleted before the pods that they protect. This can lead to a brief period in which the pods are running, but network policies that should apply to connections to and from the pods are not enforced.
Impacted products
Vendor Product Version



{
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "A security issue was discovered in Kubernetes where a malicious or compromised pod could bypass network restrictions enforced by network policies during namespace deletion. The order in which objects are deleted during namespace termination is not defined, and it is possible for network policies to be deleted before the pods that they protect. This can lead to a brief period in which the pods are running, but network policies that should apply to connections to and from the pods are not enforced.",
      },
      {
         lang: "es",
         value: "Se detectó un problema de seguridad en Kubernetes donde un pod malicioso o comprometido podía eludir las restricciones de red impuestas por las políticas de red durante la eliminación de un espacio de nombres. El orden en que se eliminan los objetos durante la terminación de un espacio de nombres no está definido, y es posible que las políticas de red se eliminen antes que los pods que protegen. Esto puede provocar que los pods se ejecuten brevemente, pero que no se apliquen las políticas de red que deberían aplicarse a las conexiones hacia y desde ellos.",
      },
   ],
   id: "CVE-2024-7598",
   lastModified: "2025-03-20T21:15:22.600",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "HIGH",
               attackVector: "ADJACENT_NETWORK",
               availabilityImpact: "NONE",
               baseScore: 3.1,
               baseSeverity: "LOW",
               confidentialityImpact: "LOW",
               integrityImpact: "NONE",
               privilegesRequired: "NONE",
               scope: "UNCHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N",
               version: "3.1",
            },
            exploitabilityScore: 1.6,
            impactScore: 1.4,
            source: "jordan@liggitt.net",
            type: "Secondary",
         },
      ],
   },
   published: "2025-03-20T17:15:37.707",
   references: [
      {
         source: "jordan@liggitt.net",
         url: "https://github.com/kubernetes/kubernetes/issues/126587",
      },
      {
         source: "jordan@liggitt.net",
         url: "https://groups.google.com/g/kubernetes-security-announce/c/67D7UFqiPRc",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         url: "http://www.openwall.com/lists/oss-security/2025/03/20/2",
      },
   ],
   sourceIdentifier: "jordan@liggitt.net",
   vulnStatus: "Awaiting Analysis",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-362",
            },
         ],
         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.


Loading…

Loading…

Loading…

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.