CyberRota Analysis
AI-GeneratedThe OAuth2 authorize endpoint in OpenAM versions 13.0.0 to 16.1.2 is vulnerable due to improper HTML escaping of request-derived values, allowing attackers to craft malicious authorization links that can execute JavaScript in the context of an OpenAM session. This vulnerability can lead to session or cookie theft, CSRF-token disclosure, and unauthorized actions using the victim's privileges. Organizations using affected versions of OpenAM should prioritize patching to version 16.1.2 to mitigate these risks.
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. From 13.0.0 until 16.1.2, the OAuth2 authorize endpoint's display=wap consent page reflects request-derived values through ConsentRequiredResource and wap/authorize.ftl without HTML escaping. An attacker can induce a user with an active OpenAM session to follow a crafted authorization link and execute JavaScript in the OpenAM origin, enabling session or cookie theft, CSRF-token disclosure, and actions with the victim's privileges. At least one registered OAuth2 client is required, but the attacker does not need to control that client. This issue is fixed in version 16.1.2.