CyberRota Analysis
AI-GeneratedOpen Access Management (OpenAM) versions prior to 16.1.1 are vulnerable due to improper handling of token identifiers and lack of integrity verification, allowing attackers to forge OAuth bearer tokens and OpenID Connect ID tokens. This vulnerability can be exploited by an attacker with access to the Core Token Store (CTS) to impersonate users or services by minting tokens with arbitrary attributes. Organizations using affected versions should prioritize this issue to mitigate the risk of unauthorized access and potential data breaches.
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
Open Access Management (OpenAM) is an access management solution. Prior to 16.1.1, OAuthTokenStore reads caller-supplied token identifiers from the shared Core Token Store (CTS) without an OAuth-only namespace, and OAuthAdapter accepts a row whose BLOB claims to contain an OAuth token without binding the trusted CTS type or verifying integrity. An attacker who can place controlled JSON in CTS under a known token identifier, such as through Push Registration followed by an anonymous SNS callback in an enabled realm, can mint OAuth bearer tokens and OpenID Connect ID tokens with chosen subject, client, realm, and scope. The flaw does not by itself create an OpenAM SSO session or grant console access. This issue is fixed in version 16.1.1.