Skip to content

Potential network policy bypass when routing IPv6 traffic

Moderate severity GitHub Reviewed Published Mar 17, 2023 in cilium/cilium • Updated Mar 24, 2023

Package

gomod github.com/cilium/cilium (Go)

Affected versions

< 1.11.15
>= 1.12.0, < 1.12.8
>= 1.13.0, < 1.13.1

Patched versions

1.11.15
1.12.8
1.13.1

Description

Impact

Under specific conditions, Cilium may misattribute the source IP address of traffic to a cluster, identifying external traffic as coming from the host on which Cilium is running. As a consequence, network policies for that cluster might be bypassed, depending on the specific network policies enabled. Only IPv6 traffic is impacted by this vulnerability.

This issue only manifests when:

  • Cilium is routing IPv6 traffic, and
  • Kube-proxy is used for service handling, and
  • NodePorts are used to route traffic to pods.

IPv6 is disabled by default. Cilium's kube-proxy replacement feature is not affected by this vulnerability.

Patches

The problem has been fixed and is available on versions >=1.11.15, >=1.12.8, >=1.13.1

Workarounds

Disable IPv6 routing (IPv6 is disabled by default).

Acknowledgements

The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to Yusuke Suzuki for both highlighting 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

@nebril nebril published to cilium/cilium Mar 17, 2023
Published to the GitHub Advisory Database Mar 17, 2023
Reviewed Mar 17, 2023
Published by the National Vulnerability Database Mar 17, 2023
Last updated Mar 24, 2023

Severity

Moderate

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
Adjacent
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
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:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

EPSS score

0.174%
(56th percentile)

CVE ID

CVE-2023-27594

GHSA ID

GHSA-8fg8-jh2h-f2hc

Source code

Credits

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