CyberRota Analysis
AI-GeneratedOpenAM versions prior to 16.1.1 are vulnerable due to a flaw in the private_key_jwt client authentication mechanism, which allows an attacker controlling a registered client to impersonate another client by leveraging exposed keys. This vulnerability can lead to unauthorized token generation across different realms within the same OpenAM instance, posing a significant security risk. Organizations using OpenAM for access management should prioritize upgrading to version 16.1.1 to mitigate this high-severity threat.
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, the private_key_jwt client authentication path uses ClientJwksResolverCache without reliably binding a cached jwks_uri resolver and verified assertion to the expected clientID in ClientCredentialsReader. An attacker controlling any registered client with published keys, including one obtained through open dynamic registration when enabled, can authenticate as another client whose keys are exposed through jwks_uri and mint tokens in that client's name across realms in the same OpenAM process. This issue is fixed in version 16.1.1.