Vulnerability from bitnami_vulndb
Published
2024-05-15 12:06
Modified
2025-05-20 10:02
Summary
Bypass of namespace restrictions in CiliumNetworkPolicy
Details

Cilium is a networking, observability, and security solution with an eBPF-based dataplane. An attacker with the ability to create or modify CiliumNetworkPolicy objects in a particular namespace is able to affect traffic on an entire Cilium cluster, potentially bypassing policy enforcement in other namespaces. By using a crafted endpointSelector that uses the DoesNotExist operator on the reserved:init label, the attacker can create policies that bypass namespace restrictions and affect the entire Cilium cluster. This includes potentially allowing or denying all traffic. This attack requires API server access, as described in the Kubernetes API Server Attacker section of the Cilium Threat Model. This issue has been resolved in Cilium versions 1.14.2, 1.13.7, and 1.12.14. As a workaround an admission webhook can be used to prevent the use of endpointSelectors that use the DoesNotExist operator on the reserved:init label in CiliumNetworkPolicies.


{
  "affected": [
    {
      "package": {
        "ecosystem": "Bitnami",
        "name": "cilium",
        "purl": "pkg:bitnami/cilium"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.12.14"
            },
            {
              "introduced": "1.13.0"
            },
            {
              "fixed": "1.13.7"
            },
            {
              "introduced": "1.14.0"
            },
            {
              "fixed": "1.14.2"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "severity": [
        {
          "score": "CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:H",
          "type": "CVSS_V3"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2023-41333"
  ],
  "database_specific": {
    "cpes": [
      "cpe:2.3:a:cilium:cilium:*:*:*:*:*:*:*:*"
    ],
    "severity": "High"
  },
  "details": "Cilium is a networking, observability, and security solution with an eBPF-based dataplane. An attacker with the ability to create or modify CiliumNetworkPolicy objects in a particular namespace is able to affect traffic on an entire Cilium cluster, potentially bypassing policy enforcement in other namespaces. By using a crafted `endpointSelector` that uses the `DoesNotExist` operator on the `reserved:init` label, the attacker can create policies that bypass namespace restrictions and affect the entire Cilium cluster. This includes potentially allowing or denying all traffic. This attack requires API server access, as described in the Kubernetes API Server Attacker section of the Cilium Threat Model. This issue has been resolved in Cilium versions 1.14.2, 1.13.7, and 1.12.14. As a workaround an admission webhook can be used to prevent the use of `endpointSelectors` that use the `DoesNotExist` operator on the `reserved:init` label in CiliumNetworkPolicies.",
  "id": "BIT-cilium-2023-41333",
  "modified": "2025-05-20T10:02:07.006Z",
  "published": "2024-05-15T12:06:29.973Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://docs.cilium.io/en/stable/security/threat-model/#kubernetes-api-server-attacker"
    },
    {
      "type": "WEB",
      "url": "https://github.com/cilium/cilium/pull/28007"
    },
    {
      "type": "WEB",
      "url": "https://github.com/cilium/cilium/security/advisories/GHSA-4xp2-w642-7mcx"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-41333"
    }
  ],
  "schema_version": "1.5.0",
  "summary": "Bypass of namespace restrictions in CiliumNetworkPolicy "
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…