GHSA-W4P9-C7H8-JVGR
non-deterministic registry configuration selection between domain and wildcard
CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-W4P9-C7H8-JVGR divulgada · CVSS 2.6 (GitHub) | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Impact
This advisory is only relevant for workload operators (see personas https://docs.edgeless.systems/contrast/next/security#protected-personas-in-a-contrast-deployment).
The registry selection algorithm of Contrast's `imagepuller` (the guest component responsible for retrieving and verifying the container images) had a bug that could lead to a wildcard match being preferred over a concrete match.
Prerequisites
Both of the following are prerequisites for this bug:
- The registry pull configuration contains both a concrete domain and its parent domain as a wildcard.
- The configuration for `.example.com` is not suitable for `registry.example.com`.
_Such configurations are very unlikely to exist in practice_: Most commonly, an affected configuration will contain a single label domain and a root wildcard. A root wildcard containing credentials would be highly risky in and of itself.
Result
The configuration for the wildcard domain would mistakenly be applied to the concrete domain, with these potential consequences:
- The registry credentials intended for `*.example.com` would be leaked to `registry.example.com`, provided it passes the CA restrictions for `.example.com`.
- The CA bundle or mirror configuration intended for `*.example.com` would be applied to `registry.example.com`, resulting in a leak of pull metadata to the audience permitted for `*.example.com` _if they would be attacking the pull on the network level_.
Patches
This bug has been patched in https://github.com/edgelesssys/contrast/pull/2682 by always preferring concrete matches to wildcard matches.
Workarounds
This bug can be worked around by removing one of the prerequisites. In particular, the wildcard entry could be replaced by a list of concrete entries.
References
Thanks to @manus-pi for reporting this issue!
Desglose de métricas
Estado del parche por paquete
La fuente no informa paquetes ni versiones corregidas.
Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/edgelesssys/contrast/security/advisories/GHSA-w4p9-c7h8-jvgrLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
