GHSA-24m5-r6hv-ccgp BIT-cilium-2023-41332 BIT-cilium-operator-2023-41332 BIT-cilium-proxy-2023-41332 BIT-hubble-2023-41332 BIT-hubble-relay-2023-41332 BIT-hubble-ui-2023-41332 BIT-hubble-ui-backend-2023-41332 CVE-2023-41332 GO-2023-2079

Specific Cilium configurations vulnerable to DoS via Kubernetes annotations

Low Go

Severity: 3.5 / 10; Low · CVSS 3.1
Exploit chance (EPSS): 0.51%; Chance of exploitation in the next 30 days. Higher than 43.77% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-755 Improper Handling of Exceptional Conditions
Fix: 1.14.2; Upgrade github.com/cilium/cilium to this version or later

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

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.

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

Affected versions

Go

Package	Vulnerable	Fixed in
github.com/cilium/cilium	`>= 1.14.0, < 1.14.2`	`1.14.2`
github.com/cilium/cilium	`< 1.12.14`	`1.12.14`
github.com/cilium/cilium	`>= 1.13.0, < 1.13.7`	`1.13.7`
github.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`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

github.com/cilium/cilium Go → `1.14.2`

go

go get github.com/cilium/cilium@v1.14.2 && go mod tidy

Severity breakdown

CVSS 3.1 3.5

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

Attack vector: Adjacent
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Weakness

CWE-755: Improper Handling of Exceptional Conditions

The product does not handle or incorrectly handles an exceptional condition.

References

Advisories

nvd.nist.gov/vuln/detail/CVE-2023-41332

Packages

github.com/cilium/cilium

Timeline

Sep 27, 2023 Published
Sep 10, 2026 Last updated by the source
Oct 31, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-fm8w-2m5w-9j7r Cilium may unexpectedly allow ingress traffic from the local namespace when a Kubernetes NetworkPolicy is configured with an ipBlock match	Medium	Also affects github.com/cilium/cilium
GHSA-w7c2-w76w-5hmj Cilium: Namespaced HTTPRoutes can redirect traffic to other namespaces	High	Also affects github.com/cilium/cilium
GHSA-q6h5-q3q6-f87x CiliumLocalRedirectPolicy addressMatcher allows cross-namespace service traffic hijacking and can break service translation	Medium	Also affects github.com/cilium/cilium
GHSA-3fcv-jvfp-m4q9 Cilium vulnerable to sensitive information disclosure and cluster disruption via local Envoy admin socket access	High	Also affects github.com/cilium/cilium
GHSA-gj49-89wh-h4gj Cillium exposes sensitive information included in the cilium-bugtool debug archive	Medium	Also affects github.com/cilium/cilium
GHSA-hxv8-4j4r-cqgv Cilium L7 proxy may bypass Kubernetes NetworkPolicy for same-node traffic	Medium	Also affects github.com/cilium/cilium
GHSA-5r23-prx4-mqg3 Cilium may not enforce host firewall policies when Native Routing, WireGuard and Node Encryption are enabled	Medium	Also affects github.com/cilium/cilium
GHSA-38pp-6gcp-rqvm Cilium with misconfigured toGroups in policies can lead to unrestricted egress traffic	Medium	Also affects github.com/cilium/cilium

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor