CyberRota Analysis
AI-GeneratedOpenBao versions prior to 2.5.4 are vulnerable in their Kerberos authentication method, where the `GET` handler inadvertently exposes a `logical.Auth` object alongside an error message. This flaw can lead to the creation of authentication tokens with default policies and TTLs, although these tokens remain inaccessible to the caller. Organizations using OpenBao for identity-based secrets management should prioritize upgrading to version 2.5.4 or implementing rate limiting as a temporary workaround to mitigate potential risks.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
OpenBao is an open source identity-based secrets management system. Prior to version 2.5.4, in OpenBao's Kerberos auth method on the `GET` handler, or when an `Authorization: Negotiate` header is supplied, the response is includes a `logical.Auth` object in addition to an error message. This results in tokens being created with only the default policy, default TTL, and no entity information, which are hidden by the returned error message. No access to these tokens by the caller occurs and the authentication token is not ever made accessible outside of `sys/raw`. This is fixed in OpenBao v2.5.4. As a workaround, users may set a rate limit quota to limit the creation of these paths. As the path is unauthenticated, it isn't possible to deny access to it.