Open Access Management (OpenAM) is an access management solution. In versions prior to 16.0.0, if the "claims_parameter_supported" parameter is activated, it is possible, thanks to the "oidc-claims-extension.groovy" script, to inject the value of one's choice into a claim contained in the id_token or in the user_info. In the request of an authorize function, a claims parameter containing a JSON file can be injected. This JSON file allows attackers to customize the claims returned by the "id_token" and "user_info" files. This allows for a very wide range of vulnerabilities depending on how clients use claims. For example, if some clients rely on an email field to identify a user, an attacker can choose the email address they want, and therefore assume any identity they choose. Version 16.0.0 fixes the issue.
Advisories
Source ID Title
Github GHSA Github GHSA GHSA-39hr-239p-fhqc OpenAM: Using arbitrary OIDC requested claims values in id_token and user_info is allowed
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

Thu, 13 Nov 2025 10:00:00 +0000

Type Values Removed Values Added
First Time appeared Openidentityplatform
Openidentityplatform openam
Vendors & Products Openidentityplatform
Openidentityplatform openam

Wed, 12 Nov 2025 19:15:00 +0000

Type Values Removed Values Added
Description Open Access Management (OpenAM) is an access management solution. In versions prior to 16.0.0, if the "claims_parameter_supported" parameter is activated, it is possible, thanks to the "oidc-claims-extension.groovy" script, to inject the value of one's choice into a claim contained in the id_token or in the user_info. In the request of an authorize function, a claims parameter containing a JSON file can be injected. This JSON file allows attackers to customize the claims returned by the "id_token" and "user_info" files. This allows for a very wide range of vulnerabilities depending on how clients use claims. For example, if some clients rely on an email field to identify a user, an attacker can choose the email address they want, and therefore assume any identity they choose. Version 16.0.0 fixes the issue.
Title OpenAM allows use of arbitrary OIDC requested claims values in id_token and user_info
Weaknesses CWE-74
References
Metrics cvssV4_0

{'score': 8.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2025-11-12T21:04:04.048Z

Reserved: 2025-10-27T15:26:14.126Z

Link: CVE-2025-64099

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2025-11-12T19:15:38.087

Modified: 2025-11-12T19:15:38.087

Link: CVE-2025-64099

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2025-11-13T09:52:22Z