CyberRota Analysis
AI-GeneratedAn internal and undocumented API endpoint allows an authenticated attacker to create API tokens for other users without proper permission checks, potentially enabling them to escalate privileges to that of a Dashboard Administrator. If the targeted user has administrative rights, the attacker could execute all administrative actions, leading to severe security implications, including potential code execution on the host system. Organizations with internal users who have elevated privileges and utilize the affected Dashboard should prioritize addressing this vulnerability to mitigate the risk of unauthorized access and control.
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
The implementation of an internal and undocumented Dashboard API endpoint (POST /api/users/~/{user}/tokens) forgot to ensure an HTTP request for creating an API Token for another user had sufficient permission to do so. Precondition for successful exploitation was a preexisting internal user (with more privileges than the attacker), the attacker knowing its login name and the attacker being able to authenticate to the Dashboard via OAuth/OIDC. The attacker would then have had to forge a token creation API request on behalf of the other user and could have authenticated and finalized the token creation with their own OAuth/OIDC credentials. In the worst case, this would mean an attacker could have become Dashboard Administrator and been able to perform all administrative actions if the preexisting internal user had administrative privileges. In combination with a separate weakness, this could have further led to code execution on the host system running the Dashboard with the privileges of the OS-User running the Dashboard server.