Package Instance

OpenBao's Inline Auth Incorrectly Redacted Headers
### Impact

OpenBao's inline auth functionality incorrectly redacted audit log entries, resulting in non-auth headers being removed and auth-related headers being retained in cleartext. This requires an attacker to compromise access to the audit device. Operators should review leaked source authentication material and rotate it as appropriate.

### Patches

This is fixed in OpenBao v2.5.4.

### Resources

https://github.com/openbao/openbao/issues/3074

OpenBao's cross-namespace lease revocation via legacy sys/revoke path bypasses ACL
# Impact

OpenBao's namespaces provide multi-tenant separation. A tenant who intentionally leaks lease identifiers can have their lease and underlying credential revoked or renewed by a user in another tenant via the legacy, undocumented `sys/revoke` and `sys/renew` endpoints.

# Patch

This will be addressed in v2.5.4.

OpenBao's Kerberos Auth Method Accumulates Unaccessible Tokens
### Impact

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`. At most this could cause storage usage.

### Patches

This is fixed in OpenBao v2.5.4. 

### Workarounds

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.

### Reporter

This was discovered by an anonymous reporter.