GHSA-2H44-X2WX-49F4
Potential HTTP policy bypass when using header rules in Cilium
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche v1.11.16 | github.com/cilium/cilium · -35 d desde divulgación | |
| Remediación | Parche v1.12.9 | github.com/cilium/cilium · -35 d desde divulgación | |
| Remediación | Parche v1.13.2 | github.com/cilium/cilium · -35 d desde divulgación | |
| Divulgación | Publicada | GHSA-2H44-X2WX-49F4 divulgada | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Detectada | Ingresó al índice |
Impact
This issue only impacts users who:
- Have a HTTP policy that applies to multiple `toEndpoints` AND
- Have an allow-all rule in place that affects only one of those endpoints
In such cases, a wildcard rule will be appended to the set of HTTP rules, which could cause bypass of HTTP policies.
Patches
This issue has been patched in Cilium 1.11.16, 1.12.9, and 1.13.2.
Workarounds
Rewrite HTTP rules for each endpoint separately. For example, if the initial rule looks like:
egress:
- toEndpoints:
- matchLabels:
k8s:kind: echo
- matchLabels:
k8s:kind: example
toPorts:
- ports:
- port: "8080"
protocol: TCP
rules:
http:
- method: "GET"It should be rewritten to:
egress:
- toEndpoints:
- matchLabels:
k8s:kind: echo
toPorts:
- ports:
- port: "8080"
protocol: TCP
rules:
http:
- method: "GET"
- toEndpoints:
- matchLabels:
k8s:kind: example
toPorts:
- ports:
- port: "8080"
protocol: TCP
rules:
http:
- method: "GET"Acknowledgements
The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @jrajahalme for investigating and fixing the issue.
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.
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
gogithub.com/cilium/cilium |
Corregida | v1.11.16, v1.12.9, v1.13.2 | -35 d · -35 d · -35 d | v1.20.4 no afectada |
1.11.16v1.11.161.12.9v1.12.91.13.2v1.13.2Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://nvd.nist.gov/vuln/detail/CVE-2023-30851https://github.com/cilium/cilium/security/advisories/GHSA-2h44-x2wx-49f4https://github.com/cilium/ciliumhttps://github.com/cilium/cilium/releases/tag/v1.11.16https://github.com/cilium/cilium/releases/tag/v1.12.9https://github.com/cilium/cilium/releases/tag/v1.13.2Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
