Description (CNA)
OpenBao is an open source identity-based secrets management system. Prior to version 2.5.2, 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. Version 2.5.2 includes an additional confirmation screen for `direct` type logins that requires manual user interaction in order to finish the authentication. 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.
Affected (CNA)
| Vendor / product | Versions |
|---|---|
| openbao / openbao | affected < 2.5.2 |
CWE
CWE-384
References
- https://github.com/openbao/openbao/security/advisories/GHSA-7q7g-x6vg-xpc3
- https://github.com/openbao/openbao/commit/e32103951925723e9787e33886ab6b6ec20f4964
- https://datatracker.ietf.org/doc/html/rfc8628#section-5.4
ADP enrichment
No English description supplied.
No references supplied.
A flaw was found in OpenBao. A missing prompt for user confirmation when logging in via the JWT/OIDC authentication method with a role configured to use `callback_mode=direct` allows an attacker to initiate an authentication request and perform a "remote phishing" attack by tricking an authenticated user into visiting a crafted URL, automatically logging the user into the session of the attacker.