Privilege escalation in Calico CNI install binary
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in v3.26.5, v3.27.3, v3.17.4, v3.18.2, v3.19.0-2.0, and 3 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In vulnerable versions of Calico (v3.27.2 and below), Calico Enterprise (v3.19.0-1, v3.18.1, v3.17.3 and below), and Calico Cloud (v19.2.0 and below), an attacker who has local access to the Kubernetes node, can escalate their privileges by exploiting a vulnerability in the Calico CNI install binary. The issue arises from an incorrect SUID (Set User ID) bit configuration in the binary, combined with the ability to control the input binary, allowing an attacker to execute an arbitrary binary with elevated privileges.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- cni-plugin
fixed in v3.26.5; From v3.27.0 · fixed in v3.27.3
- cni-plugin
fixed in v3.17.4; From v3.18.0 · fixed in v3.18.2; From v3.19.0-1.0 · fixed in v3.19.0-2.0
- cni-plugin
fixed in v19.3.0
- github.com/projectcalico/calicoGo
All versions
- github.com/projectcalico/calico/v3Go
All versions
- github.com/projectcalico/calicoGo
fixed in 3.26.5
- github.com/projectcalico/calicoGo
From 3.27.0 · fixed in 3.27.3