CVE-2023-29002

Workarounds

Disable debug mode.

Acknowledgements

The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @meyskens for investigating and fixing the issue.

For more information

If you have any questions or comments about this advisory, please reach out on 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: [email protected] - 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.

When run in debug mode, Cilium may log sensitive information.

In particular, Cilium running in debug mode will log the values of headers if they match HTTP network policy rules. This issue affects Cilium versions:

• 1.7.* to 1.10.* inclusive
• 1.11.* before 1.11.16
• 1.12.* before 1.12.9
• 1.13.* before 1.13.2

In addition, Cilium 1.12.* before 1.12.9 and 1.13.* before 1.13.2., when running in debug mode, might log secrets used by the Cilium agent. This includes TLS private keys for Ingress and GatewayAPI resources, depending on the configuration of the affected cluster. Output of the confidential data would occur at Cilium agent restart, when the secrets are modified, and on creation of Ingress or GatewayAPI resources.

CVE-2023-29002 has a CVSS score of 7.2 (High). The vector is requires local access, 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 (1.11.16, 1.12.9, 1.13.2); upgrading removes the vulnerable code path.

Kodem intelligence

This vulnerability is fixed in Cilium releases 1.11.16, 1.12.9, and 1.13.2.

1. What is CVE-2023-29002? CVE-2023-29002 is a high-severity security vulnerability in github.com/cilium/cilium (go), affecting versions >= 1.7.0, <= 1.10.0. It is fixed in 1.11.16, 1.12.9, 1.13.2.
2. How severe is CVE-2023-29002? CVE-2023-29002 has a CVSS score of 7.2 (High). 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/cilium/cilium are affected by CVE-2023-29002? github.com/cilium/cilium (go) versions >= 1.7.0, <= 1.10.0 is affected.
4. Is there a fix for CVE-2023-29002? Yes. CVE-2023-29002 is fixed in 1.11.16, 1.12.9, 1.13.2. Upgrade to this version or later.
5. Is CVE-2023-29002 exploitable, and should I be worried? Whether CVE-2023-29002 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-2023-29002 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-2023-29002?
   • Upgrade github.com/cilium/cilium to 1.11.16 or later
   • Upgrade github.com/cilium/cilium to 1.12.9 or later
   • Upgrade github.com/cilium/cilium to 1.13.2 or later

Other vulnerabilities in github.com/cilium/cilium