GHSA-XQHM-7XHV-6PPJ
Cilium secret sync name collision enables cross-namespace L7 policy bypass
CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche v1.17.18 | github.com/cilium/cilium · -27 d desde divulgación | |
| Remediación | Parche v1.18.12 | github.com/cilium/cilium · -27 d desde divulgación | |
| Remediación | Parche v1.19.6 | github.com/cilium/cilium · -27 d desde divulgación | |
| Divulgación | Publicada | GHSA-XQHM-7XHV-6PPJ divulgada · CVSS 7.3 (GitHub) | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Impact
In a cluster with SDS https://docs.cilium.io/en/stable/security/tls-visibility/#secret-discovery-service-sds enabled for L7 network policies, an attacker may be able to affect policy enforcement behaviour by exploiting name collisions between synced Secret and ConfigMap objects.
A namespaced attacker who can create a Secret or ConfigMap and a referencing CiliumNetworkPolicy may be able to choose object names that collide with a victim object. The attacker-controlled object can then overwrite the synchronized SDS object used by the victim policy, including policies using headerMatches.secret.
This can change policy enforcement behavior, allowing unauthorized traffic that should have been denied, or denying legitimate traffic that should have been allowed.
Patches
This issue affects:
- Cilium v1.17 between v1.17.0 and v1.17.17 inclusive
- Cilium v1.18 between v1.18.0 and 1.18.11 inclusive
- Cilium v1.19 between v1.19.0 and 1.19.5 inclusive
This issue has been patched in:
- Cilium v1.17.18
- Cilium v1.18.12
- Cilium v1.19.6
Workarounds
Operators can mitigate the Network Policy SDS collision by disabling policy Secret synchronization and managing referenced policy Secrets directly in the configured policy secrets namespace (`cilium-secrets` by default).
Acknowledgements
Special thanks to @robertprast for reporting this issue, @nezdolik for preparing the fix, and @youngnick for their assistance in reviewing the solution.
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/.
If you think you have found a vulnerability affecting Cilium, we strongly encourage you to report it to our security mailing list at [security@cilium.io](mailto:security@cilium.io). This is a private mailing list for the Cilium security team, and your report will be treated as top priority.
Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
gogithub.com/cilium/cilium |
Corregida | v1.17.18, v1.18.12, v1.19.6 | -27 d · -27 d · -27 d | v1.20.4 no afectada |
v1.17.181.18.12v1.18.121.19.6v1.19.6Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/cilium/cilium/security/advisories/GHSA-xqhm-7xhv-6ppjLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
