x/vulndb: potential Go vuln in github.com/cilium/cilium: CVE-2023-39347

[GoVulnBot]

CVE-2023-39347 references github.com/cilium/cilium, which may be a Go module.

Description:
Cilium is a networking, observability, and security solution with an eBPF-based dataplane. An attacker with the ability to update pod labels can cause Cilium to apply incorrect network policies. This issue arises due to the fact that on pod update, Cilium incorrectly uses user-provided pod labels to select the policies which apply to the workload in question. This can affect Cilium network policies that use the namespace, service account or cluster constructs to restrict traffic, Cilium clusterwide network policies that use Cilium namespace labels to select the Pod and Kubernetes network policies. Non-existent construct names can be provided, which bypass all network policies applicable to the construct. For example, providing a pod with a non-existent namespace as the value of the io.kubernetes.pod.namespace label results in none of the namespaced CiliumNetworkPolicies applying to the pod in question. This attack requires the attacker to have Kubernetes API Server access, as described in the Cilium Threat Model. This issue has been resolved in: Cilium versions 1.14.2, 1.13.7, and 1.12.14. Users are advised to upgrade. As a workaround an admission webhook can be used to prevent pod label updates to the k8s:io.kubernetes.pod.namespace and io.cilium.k8s.policy.* keys.

References:

• NIST: https://nvd.nist.gov/vuln/detail/CVE-2023-39347
• JSON: https://github.com/CVEProject/cvelist/tree/8e23c01bc8ca16079613b67ffe67860eec01624b/2023/39xxx/CVE-2023-39347.json
• advisory: GHSA-gj2r-phwg-6rww
• web: https://docs.cilium.io/en/latest/security/threat-model/#kubernetes-api-server-attacker
• Imported by: https://pkg.go.dev/github.com/cilium/cilium?tab=importedby

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
      vulnerable_at: 1.14.2
      packages:
        - package: cilium
description: |-
    Cilium is a networking, observability, and security solution with an eBPF-based
    dataplane. An attacker with the ability to update pod labels can cause Cilium to
    apply incorrect network policies. This issue arises due to the fact that on pod
    update, Cilium incorrectly uses user-provided pod labels to select the policies
    which apply to the workload in question. This can affect Cilium network policies
    that use the namespace, service account or cluster constructs to restrict
    traffic, Cilium clusterwide network policies that use Cilium namespace labels to
    select the Pod and Kubernetes network policies. Non-existent construct names can
    be provided, which bypass all network policies applicable to the construct. For
    example, providing a pod with a non-existent namespace as the value of the
    `io.kubernetes.pod.namespace` label results in none of the namespaced
    CiliumNetworkPolicies applying to the pod in question. This attack requires the
    attacker to have Kubernetes API Server access, as described in the Cilium Threat
    Model. This issue has been resolved in: Cilium versions 1.14.2, 1.13.7, and
    1.12.14. Users are advised to upgrade. As a workaround an admission webhook can
    be used to prevent pod label updates to the `k8s:io.kubernetes.pod.namespace`
    and `io.cilium.k8s.policy.*` keys.
cves:
    - CVE-2023-39347
references:
    - advisory: https://github.com/cilium/cilium/security/advisories/GHSA-gj2r-phwg-6rww
    - web: https://docs.cilium.io/en/latest/security/threat-model/#kubernetes-api-server-attacker

[jba]

Vulnerability in tool.

[gopherbot]

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

[jba]

Duplicate of #2078