x/vulndb: potential Go vuln in github.com/cilium/cilium: GHSA-4xp2-w642-7mcx

[GoVulnBot]

In GitHub Security Advisory GHSA-4xp2-w642-7mcx, there is a vulnerability in the following Go packages or modules:

Unit	Fixed	Vulnerable Ranges
github.com/cilium/cilium	1.12.14	< 1.12.14

Cross references:

• Module github.com/cilium/cilium appears in issue x/vulndb: potential Go vuln in github.com/cilium/cilium: GHSA-c66w-hq56-4q97 #393 EFFECTIVELY_PRIVATE
• Module github.com/cilium/cilium appears in issue x/vulndb: potential Go vuln in github.com/cilium/cilium: CVE-2022-29178 #457 EFFECTIVELY_PRIVATE
• Module github.com/cilium/cilium appears in issue x/vulndb: potential Go vuln in github.com/cilium/cilium: CVE-2022-29179 #458 EFFECTIVELY_PRIVATE
• Module github.com/cilium/cilium appears in issue x/vulndb: potential Go vuln in github.com/cilium/cilium: GHSA-wc5v-r48v-g4vh #530 NOT_GO_CODE
• Module github.com/cilium/cilium appears in issue x/vulndb: potential Go vuln in github.com/cilium/cilium: GHSA-pfhr-pccp-hwmh #959 EFFECTIVELY_PRIVATE
• Module github.com/cilium/cilium appears in issue x/vulndb: potential Go vuln in github.com/cilium/cilium: GHSA-4hc4-pgfx-3mrx #1642 NOT_GO_CODE
• Module github.com/cilium/cilium appears in issue x/vulndb: potential Go vuln in github.com/cilium/cilium: GHSA-8fg8-jh2h-f2hc #1643 EFFECTIVELY_PRIVATE
• Module github.com/cilium/cilium appears in issue x/vulndb: potential Go vuln in github.com/cilium/cilium: GHSA-r5x6-w42p-jhpp #1644 EFFECTIVELY_PRIVATE
• Module github.com/cilium/cilium appears in issue x/vulndb: potential Go vuln in github.com/cilium/cilium: CVE-2023-29002 #1730 EFFECTIVELY_PRIVATE
• Module github.com/cilium/cilium appears in issue x/vulndb: potential Go vuln in github.com/cilium/cilium: GHSA-2h44-x2wx-49f4 #1785 EFFECTIVELY_PRIVATE
• Module github.com/cilium/cilium appears in issue x/vulndb: potential Go vuln in github.com/cilium/cilium: CVE-2023-34242 #1862 EFFECTIVELY_PRIVATE

See doc/triage.md for instructions on how to triage this report.

modules:
    - module: github.com/cilium/cilium
      versions:
        - fixed: 1.12.14
      vulnerable_at: 1.12.13
      packages:
        - package: github.com/cilium/cilium
    - module: github.com/cilium/cilium
      versions:
        - introduced: 1.13.0
          fixed: 1.13.7
      vulnerable_at: 1.13.6
      packages:
        - package: github.com/cilium/cilium
    - module: github.com/cilium/cilium
      versions:
        - introduced: 1.14.0
          fixed: 1.14.2
      vulnerable_at: 1.14.1
      packages:
        - package: github.com/cilium/cilium
summary: Cilium vulnerable to bypass of namespace restrictions in CiliumNetworkPolicy
description: |-
    ### Impact

    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](https://docs.cilium.io/en/stable/security/threat-model/#kubernetes-api-server-attacker)
    section of the Cilium Threat Model.

    ### Patches

    This issue was patched in https://github.com/cilium/cilium/pull/28007

    This issue affects:

    - Cilium <= v1.14.1
    - Cilium <= v1.13.6
    - Cilium <= v1.12.13

    This issue has been resolved in:

    - Cilium v1.14.2
    - Cilium v1.13.7
    - Cilium v1.12.14

    ### Workarounds

    An admission webhook can be used to prevent the use of `endpointSelector`s that
    use the `DoesNotExist` operator on the `reserved:init` label in
    CiliumNetworkPolicies.

    ### Acknowledgements The Cilium community has worked together with members of
    Palantir and Isovalent to prepare these mitigations. Special thanks to @odinuge
    for reporting this issue and @joestringer for the fix.

    ### For more information If you have any questions or comments about this
    advisory, please reach out on
    [Slack](https://docs.cilium.io/en/latest/community/community/#slack).

    If you think you have found a vulnerability in Cilium, we strongly encourage you
    to report it to our private security mailing list at
    [security@cilium.io](mailto:security@cilium.io) first, before disclosing it in
    any public forum. This is a private mailing list for Cilium's internal security
    team, and your report will be treated as top priority.
cves:
    - CVE-2023-41333
ghsas:
    - GHSA-4xp2-w642-7mcx
references:
    - advisory: https://github.com/cilium/cilium/security/advisories/GHSA-4xp2-w642-7mcx
    - fix: https://github.com/cilium/cilium/pull/28007
    - web: https://docs.cilium.io/en/stable/security/threat-model/#kubernetes-api-server-attacker
    - advisory: https://github.com/advisories/GHSA-4xp2-w642-7mcx

[jba]

Vulnerability in tool.

[gopherbot]

Change https://go.dev/cl/531705 mentions this issue: data/excluded: batch add 18 excluded reports

[gopherbot]

Change https://go.dev/cl/592763 mentions this issue: data/reports: unexclude 75 reports

[gopherbot]

Change https://go.dev/cl/606791 mentions this issue: data/reports: unexclude 20 reports (11)