CVE-2022-28224 — calico
MEDIUMCVE-2022-28224 is a medium-severity (CVSS 5.5) Information Exposure vulnerability in github.com/projectcalico/calico. A fix is available for github.com/projectcalico/calico — see the affected versions and patch details below.
Calico and Calico Enterprise may be vulnerable to route hijacking with the floating IP feature
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/projectcalico/calico🐹github.com/projectcalico/calico🐹github.com/projectcalico/calicoReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Clusters using Calico (version 3.22.1 and below), Calico Enterprise (version 3.12.0 and below), may be vulnerable to route hijacking with the floating IP feature. Due to insufficient validation, a privileged attacker may be able to set a floating IP annotation to a pod even if the feature is not enabled. This may allow the attacker to intercept and reroute traffic to their compromised pod.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/projectcalico/calico | ≥ 3.22.0&&< 3.22.2 | 3.22.2go get github.com/projectcalico/calico@v3.22.2 |
| 🐹Go | github.com/projectcalico/calico | ≥ 3.21.0&&< 3.21.5 | 3.21.5go get github.com/projectcalico/calico@v3.21.5 |
| 🐹Go | github.com/projectcalico/calico | all versions | 3.20.5go get github.com/projectcalico/calico@v3.20.5 |
Affected Products
calicotigeracalico enterprisetigeraDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/projectcalico/calico, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/projectcalico/calico to 3.22.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-28224 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is CVE-2022-28224 in your dependencies?
Find it across Go, including transitive dependencies.