cve.bz

CVE-2023-39347 cilium cilium

9.0 criticalExploit referenceEPSS 0.6%Fix available

Critical (9.0) in cilium cilium. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/cilium/cilium 1.12.14, 1.13.7, 1.14.2.

On this page
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.

Severity

CVSS 3.1

9.0 critical
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 48th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2024-09-24. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-345 Insufficient Verification of Data Authenticity
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-39347 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-39347?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-39347?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-39347 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
cilium:ciliumbefore 1.12.14
cilium:ciliumfrom 1.13.0 before 1.13.7
cilium:ciliumfrom 1.14.0 before 1.14.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-gj2r-phwg-6rwwGogithub.com/cilium/cilium>=1.13.0 <1.13.71.13.7
GHSA-gj2r-phwg-6rwwGogithub.com/cilium/cilium>=1.14.0 <1.14.21.14.2
GHSA-gj2r-phwg-6rwwGogithub.com/cilium/cilium<1.12.141.12.14
GO-2023-2078Gogithub.com/cilium/cilium<1.12.14
>=1.13.0 <1.13.7
>=1.14.0 <1.14.2
1.12.14, 1.13.7, 1.14.2

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-345 (12).

References

Check your stackJSON