llamaCVEVulnerability Intelligence
/
Advisory · GitHub · Go · github.com/juju/juju

GHSA-W5FQ-8965-C969

Juju: CloudSpec method leaking cloud credentials

Parche disponible
Descargar PNG JSON
CVSS
—
critical
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versióncommit d395054
Exposición223 dDesde la divulgación, 10 abr 2026, 4:00 p. m.
Detección220 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Modificada
Explotación
Remediación
Monitoreo
Detectada
10 abr 26
25 jun 26
17 nov 26
19 nov 26
10 abr 26
5 jun 26
31 jul 26
25 sept 26
19 nov 26
FechaFaseEventoDetalle
Divulgación Publicada GHSA-W5FQ-8965-C969 divulgada
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Resumen
Descripción del advisory
Texto original · GitHub · en inglés
Impact

If a user has login permission to a controller and knows the controller model UUID, they can call the CloudSpec method on the Controller facade and get cloud credentials used to bootstrap the controller.

The CloudSpec API is called by workers running in the controller to maintain connection to the cloud - this aspect is not the issue. The API is also called by the CLI when killing (force destroying a controller with `juju kill-controller`). This is the problematic aspect. The API is exposed to any client caller where that client has nothing more than logon permission on the controller. What should happen is that getting access to the credential should be limited to those client connections where the authenticated user has superuser or model admin permission.

This affect 2.9, 3.6, 4.0.6 (snap from 4.0/edge channel).

The fix will allow non-confidential, public information like cloud endpoint etc to be read, but only controller superusers or model admins will be able to see the credential details.

Patches

No patch exists.

Workarounds

The only mitigation is to restrict ingress to the controller API port 17070 on all controller machines (for vm deployments) or the controller service (for k8s deployments). The Juju CLI and other clients like libjuju or JAAS require ingress to port 17070 so any restricted access will need to take into account those access requirements.

Versiones

Rangos afectados

Afectada Corregida
github.com/juju/juju< 0.0.0-20260408003526-d395054dc2c3
0.0.0-20260408003526-d395054dc2c3
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
Gogithub.com/juju/juju
Corregida commit d395054 — —
Versiones corregidascommit d395054
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Advisoryhttps://nvd.nist.gov/vuln/detail/CVE-2026-5412
Otrahttps://github.com/juju/juju/security/advisories/GHSA-w5fq-8965-c969
Otrahttps://github.com/juju/juju/pull/22205
Otrahttps://github.com/juju/juju/pull/22206
Otrahttps://github.com/juju/juju

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.