GHSA-7Q7G-X6VG-XPC3
OpenBao lacks user confirmation for OIDC direct callback mode
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche v0.1.0 | github.com/openbao/openbao · -3985 d desde divulgación | |
| Divulgación | Publicada | GHSA-7Q7G-X6VG-XPC3 divulgada | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Detectada | Ingresó al índice |
Impact
OpenBao does not prompt for user confirmation when logging in via JWT/OIDC and a role with `callback_mode` set to `direct`.
This allows an attacker to start an authentication request and perform "remote phishing" by having the victim visit the URL and automatically log-in to the session of the attacker. Despite being based on the authorization code flow, the `direct` mode calls back directly to the API and allows an attacker to poll for an OpenBao token until it is issued.
### Patches
Version 2.5.2 includes an additional confirmation screen for `direct` type logins that requires manual user interaction in order to finish the authentication.
### Workarounds
This issue can be worked around either by removing any roles with `callback_mode=direct` or enforcing confirmation for every session on the token issuer side for the Client ID used by OpenBao.
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
gogithub.com/openbao/openbao |
Corregida | v0.1.0 | -3985 d | — |
commit e321039v0.1.0Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://nvd.nist.gov/vuln/detail/CVE-2026-33757https://github.com/openbao/openbao/security/advisories/GHSA-7q7g-x6vg-xpc3https://github.com/openbao/openbao/commit/e32103951925723e9787e33886ab6b6ec20f4964https://datatracker.ietf.org/doc/html/rfc8628#section-5.4https://github.com/openbao/openbaoLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
