Skip to content
Noroxi
CVE-2023-41332· NVD / CVE Program· CNA GitHub_M

Denial of service via Kubernetes annotations in specific Cilium configurations

Cilium is a networking, observability, and security solution with an eBPF-based dataplane. 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) or `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. This issue has been resolved in Cilium versions 1.14.2, 1.13.7, and 1.12.14. Users unable to upgrade can avoid this denial of service attack by enabling the Layer 7 proxy.

LowCVSS 3.5 · v3.1—No exploit Fix available
Published
Sep 27, 2023
Updated
Jun 17, 2026
EPSS
0.5% · 42th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

14

Monitor

Low priority for now.

CVSS
14 / 40 · 3.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
3.5
CNA · GitHub_M
3.5
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
ciliumcilium

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • cilium ciliumbefore 1.12.14
  • cilium cilium1.13.0 and later · before 1.13.7
  • cilium cilium1.14.0 and later · before 1.14.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • cilium cilium

    • >= 1.14.0, < 1.14.2, >= 1.13.0, < 1.13.7, < 1.12.14affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gogithub.com/cilium/ciliumfrom 1.13.0 · before 1.13.71.13.7
Gogithub.com/cilium/ciliumfrom 1.14.0 · before 1.14.21.14.2
Gogithub.com/cilium/ciliumbefore 1.12.141.12.14

Same product

cilium: all records

Other highest-scoring records for the same primary product.

  • CVE-2023-27595Cilium eBPF filters may be temporarily removed during agent restart
    39Monitor
  • CVE-2023-39347Cilium NetworkPolicy bypass via pod labels
    36Monitor
  • CVE-2026-56742Cilium: Namespaced HTTPRoutes can redirect traffic to other namespaces
    35Monitor
  • CVE-2026-49445Cilium: Sensitive information disclosure and cluster disruption via local Envoy admin socket access
    35Monitor
  • CVE-2024-47825CIDR deny policies may not take effect when a more narrow CIDR allow is present
    34Monitor
  • CVE-2023-41333Bypass of namespace restrictions in CiliumNetworkPolicy
    32Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go:github.com/cilium/cilium1.12.14Package registry (OSV)
Go:github.com/cilium/cilium1.13.7Package registry (OSV)
Go:github.com/cilium/cilium1.14.2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone on the same network segment can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
low · the service can be disrupted
Attack vector
Adjacent
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
Low

Weakness class (CWE)

CWE-755 · Improper Handling of Exceptional Conditions

CVSS vector

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

All records