Skip to content

Debug mode leaks confidential data in Cilium

High severity GitHub Reviewed Published Apr 18, 2023 in cilium/cilium • Updated Nov 12, 2023

Package

gomod github.com/cilium/cilium (Go)

Affected versions

>= 1.7.0, <= 1.10.0
>= 1.11.0, < 1.11.16
>= 1.12.0, < 1.12.9
>= 1.13.0, < 1.13.2

Patched versions

1.11.16
1.12.9
1.13.2

Description

Impact

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.

Patches

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

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.

References

@joestringer joestringer published to cilium/cilium Apr 18, 2023
Published by the National Vulnerability Database Apr 18, 2023
Published to the GitHub Advisory Database Apr 19, 2023
Reviewed Apr 19, 2023
Last updated Nov 12, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
High
Privileges required
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N

EPSS score

0.043%
(10th percentile)

Weaknesses

CVE ID

CVE-2023-29002

GHSA ID

GHSA-pg5p-wwp8-97g8

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.