ServiceAccount token disclosure via Azure IPAM CNI plugin logs
- 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 3.32.0, 3.21.7, 3.22.3, 22.4.0, 3.31.6, and 1 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: partial
Summary
When Calico is configured with the Azure IPAM plugin, the Calico CNI binary mutates the incoming CNI configuration to attach subnet information before delegating to the IPAM plugin. After mutating, the Azure IPAM helper logs the entire unmarshaled configuration map (stdinData) at INFO level to /var/log/calico/cni/cni.log on every CNI ADD and DEL invocation — once per pod scheduled or terminated on the node. When the cluster is deployed using token-based Kubernetes authentication, this log entry contains the ServiceAccount token, client key, and certificate authority in plaintext. Any principal with read access to /var/log/calico/cni/cni.log on a node can read these logs and extract the credentials, which grant cluster-wide Calico networking admin privileges.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Tigera Calico
fixed in 3.32.0
- Tigera Calico Enterprise
fixed in 3.21.7; From 3.22.0 · fixed in 3.22.3
- Tigera Calico Cloud
fixed in 22.4.0
- github.com/projectcalico/calicoGo
From 2.0.0 · fixed in 3.31.6
- github.com/projectcalico/calicoGo
fixed in 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f
- github.com/projectcalico/calico/v3Go
All versions