GHSA-pwqm-x5x6-5586: Weak Encryption
First published: Thu Mar 28 2024(Updated: )
### Impact Users of [IPsec transparent encryption](https://docs.cilium.io/en/stable/security/network/encryption-ipsec/) in Cilium may be vulnerable to cryptographic attacks that render the transparent encryption ineffective. In particular, Cilium is vulnerable to the following attacks by a man-in-the-middle attacker: - Chosen plaintext attacks - Key recovery attacks - Replay attacks These attacks are possible due to an ESP sequence number collision when multiple nodes are configured with the same key. Fixed versions of Cilium use unique keys for each IPsec tunnel established between nodes, resolving all of the above attacks. **Important:** After upgrading, users must perform a key rotation using the instructions [here](https://docs.cilium.io/en/latest/security/network/encryption-ipsec/#key-rotation) to ensure that they are no longer vulnerable to this issue. Please note that the key rotation instructions have recently been updated, and users must use the new instructions to properly establish secure IPsec tunnels. To validate that the new instructions have been followed properly, ensure that the IPsec Kubernetes secret contains a "+" sign. ### Patches All prior versions of Cilium that support IPsec transparent encryption (Cilium 1.4 onwards) are affected by this issue. Patched versions: - Cilium 1.15.3 - Cilium 1.14.9 - Cilium 1.13.14 ### Workarounds There is no workaround to this issue. IPsec transparent encryption users are strongly encouraged to upgrade. ### Acknowledgements The Cilium community has worked together with members of Cure53 and Isovalent to prepare these mitigations. Special thanks to @NikAleksandrov and @pchaigno for their work on remediating the issue. Thanks to Marsh Ray, Senior Software Developer at Microsoft, for input and guidance on the fix. ### For more information If you have any questions or comments about this advisory, please reach out on [Slack](https://docs.cilium.io/en/latest/community/community/#slack). As usual, if you think you found a related vulnerability, we strongly encourage you to report security vulnerabilities to our private security mailing list: [security@cilium.io](mailto:security@cilium.io) - first, before disclosing them in any public forums. This is a private mailing list where only members of the Cilium internal security team are subscribed to, and is treated as top priority.
| Affected Software | Affected Version | How to fix |
|---|---|---|
| go/github.com/cilium/cilium | >=1.15.0<=1.15.2 | 1.15.3 |
| go/github.com/cilium/cilium | >=1.14.0<=1.14.7 | 1.14.9 |
| go/github.com/cilium/cilium | >=1.4.0<=1.13.13 | 1.13.14 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://github.com/cilium/cilium/security/advisories/GHSA-pwqm-x5x6-5586
- https://nvd.nist.gov/vuln/detail/CVE-2024-28860
- https://github.com/cilium/cilium/commit/311fbce5280491cddceab178d83b06fa23688c72
- https://github.com/cilium/cilium/commit/a1742b478306fa256cd27df1039dfae0537b4149
- https://github.com/cilium/cilium/commit/a652c123331852cca90c74202f993d4170fd37fa
- https://docs.cilium.io/en/stable/security/network/encryption-ipsec
- https://github.com/advisories/GHSA-pwqm-x5x6-5586 (Advisory)
- https://pkg.go.dev/vuln/GO-2024-2666
- agent/weakness
- agent/references
- agent/severity
- agent/first-publish-date
- agent/event
- agent/type
- agent/softwarecombine
- agent/description
- agent/last-modified-date
- collector/github-advisory
- source/GitHub
- alias/GHSA-pwqm-x5x6-5586
- alias/CVE-2024-28860
- agent/software-canonical-lookup
- agent/tags
- collector/github-advisory-latest
- package-manager/go