GHSA-pfhr-pccp-hwmh GO-2022-0959

Network Policies & (Clusterwide) Cilium Network Policies with namespace label selectors may unexpectedly select pods with maliciously crafted labels

Medium Go

Severity: 4.3 / 10; Medium · CVSS 3.1
Exploit chance (EPSS): —; No score published
Known exploited: No; Not in CISA's catalog
Weakness: —; Not classified
Fix: 1.10.14; Upgrade github.com/cilium/cilium to this version or later

Description

Impact

If a user has Network Policies with namespace selectors selecting labels of namespaces, or (clusterwide) Cilium Network Policies matching on namespace labels, then it is possible for an attacker with Kubernetes pod deploy rights (either directly or indirectly via higher-level APIs such as Deployment, Daemonset etc) to craft additional pod labels such that the pod is selected by another policy that exists rather than the expected policy.

Patches

The problem has been fixed and is available on versions >=1.10.14, >=1.11.8, >=1.12.1

Workarounds

There are no workarounds available.

Acknowledgements

The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to Sander Mathijssen for not only highlighting the issue but also proposing a resolution.

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.10.14`	`1.10.14`
github.com/cilium/cilium	`>= 1.11.0, < 1.11.8`	`1.11.8`
github.com/cilium/cilium	`>= 1.12.0, < 1.12.1`	`1.12.1`
github.com/cilium/cilium	`< 1.10.14` `>= 1.11.0, < 1.11.8` `>= 1.12.0, < 1.12.1`	`1.10.14` `1.11.8` `1.12.1`

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

go

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

Severity breakdown

CVSS 3.1 4.3

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

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

References

Packages

github.com/cilium/cilium

Timeline

Aug 30, 2022 Published
Sep 10, 2026 Last updated by the source

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