Skip to content
Noroxi
OSV ecosystem advisory

GHSA-c66w-hq56-4q97: Network policy may be bypassed by some ICMP Echo Requests

Low—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Fixed version: github.com/cilium/cilium (Go) 1.7.15, 1.8.8, 1.9.5.

Low priority for now. Upgrade to github.com/cilium/cilium (Go) 1.7.15, 1.8.8, 1.9.5 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: OSV

## Impact Under certain conditions, ICMP Echo Request sent to a Cilium endpoint from an actor may bypass a network policy which _disallows_ access from the actor to the endpoint, but _allows_ from the endpoint to the actor. This does _NOT_ apply to UDP and TCP traffic. The actor is either a pod or a cluster host or a remote host. The following conditions must be met: 1. Network policies have been created which: a) do not allow access from the actor to the endpoint; b) allow access from the endpoint to the actor and does not specify neither protocol nor port. 2. The endpoint has sent ICMP Echo Request to the actor with the ICMP identifier X. 3. The actor sends ICMP Echo Request to the endpoint with the same ICMP identifier X. 4. The request from the actor (3.) is sent before the Cilium's conntrack GC has removed the previously created conntrack entry (2.). ## Detailed description See https://github.com/cilium/cilium/commit/dfb008a9099c4da1e0fd964c899c43ee13280b0e (v1.9.x), https://github.com/cilium/cilium/commit/ff6ebae6efca1bd991302b464dea428512823e79 (v1.8.x), https://github.com/cilium/cilium/commit/472bbeff75161979c317ab21d563f826291b5f37 (v1.7.x). ## Example ``` $ kubectl run server --image=quay.io/cilium/net-test:v1.0.0 --restart=Never -- sleep 3600 $ kubectl run client --image=quay.io/cilium/net-test:v1.0.0 --restart=Never -- sleep 3600 $ cat <<EOF | kubectl apply -f apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: server-netpol # allow client->server spec: podSelector: matchLabels: run: server ingress: - from: - podSelector: matchLabels: run: client policyTypes: - Ingress --- apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: client-netpol # deny any->client spec: podSelector: matchLabels: run: client policyTypes: - Ingress EOF $ kubectl exec -ti server -- xping -c1 -x666 $CLIENT_POD_IP PING 10.154.0.50 (10.154.0.50): 56 data bytes ^C --- 10.154.0.50 ping statistics --- 1 packets transmitted, 0 packets received, 100% packet loss <--- "client-netpol" policy denied command terminated with exit code 1 $ kubectl exec -ti client -- xping -c1 -x666 $SERVER_POD_IP PING 10.154.1.16 (10.154.1.16): 56 data bytes 64 bytes from 10.154.1.16: seq=0 ttl=60 time=0.822 ms --- 10.154.1.16 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss <--- "server-netpol" policy allowed round-trip min/avg/max = 0.822/0.822/0.822 ms $ kubectl exec -ti server -- xping -c1 -x666 $CLIENT_POD_IP PING 10.154.0.50 (10.154.0.50): 56 data bytes 64 bytes from 10.154.0.50: seq=0 ttl=60 time=0.527 ms --- 10.154.0.50 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss <--- "client-netpol" policy bypassed round-trip min/avg/max = 0.527/0.527/0.527 ms ``` ## For more information If you have any questions or comments about this advisory: - Open an issue in [Cilium Issues](https://github.com/cilium/cilium/issues) - Email us at security@cilium.io

Published
May 21, 2021
Updated
Aug 21, 2024
EPSS
—
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · —

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow GHSA-c66w-hq56-4q97

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
Gogithub.com/cilium/cilium

Package-level exposure

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

EcosystemPackageAffected rangeFix
Gogithub.com/cilium/ciliumfrom 1.7.8 · before 1.7.151.7.15
Gogithub.com/cilium/ciliumfrom 1.8.3 · before 1.8.81.8.8
Gogithub.com/cilium/ciliumfrom 1.9.0 · before 1.9.51.9.5

Same product

Go: all records

Other highest-scoring records for the same primary product.

  • GHSA-pfhr-pccp-hwmhNetwork Policies & (Clusterwide) Cilium Network Policies with namespace label selectors may unexpectedly select pods with maliciously crafted labels
    17Monitor
  • GHSA-wc5v-r48v-g4vhCilium host policy bypass in endpoint-routes mode with dual-stack
    13Monitor
  • GO-2022-0959Network Policies & (Clusterwide) Cilium Network Policies with namespace label selectors may unexpectedly select pods with maliciously…
    0Monitor

Published before and after this one in the same product

  • Later →GO-2022-0393Aug 21, 2024 · Network policy may be bypassed by some ICMP Echo Requests in github.com/cilium/cilium
    0Monitor

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.7.15Package registry (OSV)
Go:github.com/cilium/cilium1.8.8Package registry (OSV)
Go:github.com/cilium/cilium1.9.5Package 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.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records