x/vulndb: potential Go vuln in github.com/cilium/cilium: GHSA-24m5-r6hv-ccgp

[GoVulnBot]

In GitHub Security Advisory GHSA-24m5-r6hv-ccgp, there is a vulnerability in the following Go packages or modules:

Unit	Fixed	Vulnerable Ranges
github.com/cilium/cilium	1.13.7	>= 1.13.0, < 1.13.7

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:
        - 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:
        - fixed: 1.12.14
      vulnerable_at: 1.12.13
      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: Specific Cilium configurations vulnerable to DoS via Kubernetes annotations
description: |-
    ### Impact

    In Cilium clusters where Cilium's Layer 7 proxy has been disabled, creating
    workloads with

    - `policy.cilium.io/proxy-visibility` annotations (in Cilium >= v1.13)
    - `io.cilium.proxy-visibility` annotations (in Cilium <= v1.12)

    causes the Cilium agent to segfault on the node to which the workload is
    assigned.

    Existing traffic on the affected node will continue to flow, but the Cilium
    agent on the node will not able to process changes to workloads running on the
    node. This will also prevent workloads from being able to start on the affected
    node. The denial of service will be limited to the node on which the workload is
    scheduled, however an attacker may be able to schedule workloads on the node of
    their choosing, which could lead to targeted attacks.

    ### Patches

    [Pull request with fix](https://github.com/cilium/cilium/pull/27597)

    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

    Users can avoid this denial of service attack by enabling the Layer 7 proxy.

    ### 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).

    As usual, if you think you found a related vulnerability, we strongly encourage
    you to report security vulnerabilities to our private security mailing list:
    [security@cilium.io](mailto:security@cilium.io) - first, before disclosing them
    in any public forums. This is a private mailing list where only members of the
    Cilium internal security team are subscribed to, and is treated as top priority.
cves:
    - CVE-2023-41332
ghsas:
    - GHSA-24m5-r6hv-ccgp
references:
    - advisory: https://github.com/cilium/cilium/security/advisories/GHSA-24m5-r6hv-ccgp
    - fix: https://github.com/cilium/cilium/pull/27597
    - advisory: https://github.com/advisories/GHSA-24m5-r6hv-ccgp

[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)