CVE-2022-28224

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.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2022-28224 has a CVSS score of 5.5 (Medium). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.22.2, 3.21.5, 3.20.5); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2022-28224? CVE-2022-28224 is a medium-severity improper input validation vulnerability in github.com/projectcalico/calico (go), affecting versions >= 3.22.0, < 3.22.2. It is fixed in 3.22.2, 3.21.5, 3.20.5. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. How severe is CVE-2022-28224? CVE-2022-28224 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/projectcalico/calico are affected by CVE-2022-28224? github.com/projectcalico/calico (go) versions >= 3.22.0, < 3.22.2 is affected.
4. Is there a fix for CVE-2022-28224? Yes. CVE-2022-28224 is fixed in 3.22.2, 3.21.5, 3.20.5. Upgrade to this version or later.
5. Is CVE-2022-28224 exploitable, and should I be worried? Whether CVE-2022-28224 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-28224 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-28224?
   • Upgrade github.com/projectcalico/calico to 3.22.2 or later
   • Upgrade github.com/projectcalico/calico to 3.21.5 or later
   • Upgrade github.com/projectcalico/calico to 3.20.5 or later