CyberRota Analysis
AI-GeneratedOpenBao versions prior to 2.5.5 are vulnerable to a denial-of-service attack, where an authenticated user with write access can cause the server to crash by improperly configuring derived keys for asymmetric types. This vulnerability arises from a double-unlocking of a mutex in the key management process, leading to a server panic and no HTTP response. Organizations using OpenBao for secrets management should prioritize upgrading to version 2.5.5 to mitigate this risk.
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 2.5.5, an authenticated OpenBao caller with write access to transit/keys/* could terminate the server process by setting derived to true while the type parameter selected rsa-, ecdsa-, or ed25519. The Transit policy creation path in builtin/logical/transit/backend.go and sdk/helper/keysutil/policy.go could reach an error path that double-unlocked a mutex while handling this invalid asymmetric derived-key combination, causing a panic, no HTTP response, process exit, and denial of service. JSON and HCL key-creation requests can express the triggering combination. This issue is fixed in version 2.5.5.