CVE-2025-64099: OpenAM Using Arbitrary OIDC Requested Claims Vulnerability

HIGH
Advisory Identifier: GHSA-39hr-239p-fhqc
Share
CWE-94 CWE-74
Published
Advisory Summary

CVE-2025-64099 is a HIGH using arbitrary oidc requested claims vulnerability (CWE-94: Improper Control of Generation of Code ('Code Injection')) affecting OpenAM libraries in the Maven ecosystem. The issue involves using arbitrary oidc requested claims values in id_token and user_info is allowed. Remediation is available by upgrading affected packages to version 16.0.3.

CVE-2025-64099 at a Glance

CVE Identifier CVE-2025-64099
GHSA Identifier GHSA-39hr-239p-fhqc
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-94: Improper Control of Generation of Code ('Code Injection')
Affected Product OpenAM
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2025-64099

To remediate this vulnerability, upgrade all affected OpenAM dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

org.openidentityplatform.openam:openam-oauth2 fixed: 16.0.3 
<dependency>
    <groupId>org.openidentityplatform.openam</groupId>
    <artifactId>openam-oauth2</artifactId>
    <version>16.0.3</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree -Dincludes=org.openidentityplatform.openam

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2025-64099, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=org.openidentityplatform.openam

Analyze the terminal output to locate any version of OpenAM in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 16.0.3), your application is affected.

Note: The mvn dependency:tree -Dincludes=org.openidentityplatform.openam command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-94: Improper Control of Generation of Code ('Code Injection'), where the product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. In OpenAM, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary If the "claims_parameter_supported" parameter is activated, it is possible through the "oidc-claims-extension.groovy" script, to inject the value of choice into a claim contained in the id_token or in the user_info. Authorization function requests do not prevent a claims parameter containing a JSON file to be injected. This JSON file allows users to customize 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, users can choose to entera any email address, and therefore assume any chosen identity.

CVE-2025-64099 Affected OpenAM Versions

1 component(s)
Fixed Versions:
16.0.3
Product / Package Ecosystem Affected Versions Fixed Version
org.openidentityplatform.openam:openam-oauth2
maven/org.openidentityplatform.openam/openam-oauth2
Maven
< 16.0.3
16.0.3

References

GitHub Advisory / Wiki ADVISORY
https://github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-39hr-239p-fhqc
NVD — CVE-2025-64099 NVD
https://nvd.nist.gov/vuln/detail/CVE-2025-64099
Security Fix Commit FIX COMMIT
https://github.com/OpenIdentityPlatform/OpenAM/commit/4254b34b2b8b4867f2e7fccfac73904213d48510
OpenAM Source Repository REPOSITORY
https://github.com/OpenIdentityPlatform/OpenAM
OpenAM Release RELEASE
https://github.com/OpenIdentityPlatform/OpenAM/releases/tag/16.0.3

Frequently Asked Questions

What is CVE-2025-64099?
CVE-2025-64099 is a security vulnerability in OpenAM involving Using arbitrary OIDC requested claims values in id_token and user_info is allowed under CWE-94: Improper Control of Generation of Code ('Code Injection').
Which OpenAM versions are affected?
Affected versions include releases prior to 16.0.3 across affected packages: org.openidentityplatform.openam:openam-oauth2.
What version fixes CVE-2025-64099?
Upgrading to 16.0.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is openam-oauth2 affected?
Yes, org.openidentityplatform.openam:openam-oauth2 is affected in releases prior to 16.0.3. Upgrade your dependency to 16.0.3 or later.
What CWE is associated with CVE-2025-64099?
CVE-2025-64099 is classified under CWE-94: Improper Control of Generation of Code ('Code Injection') (The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.).
How can I check Maven dependencies for CVE-2025-64099?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.openidentityplatform.openam'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-39hr-239p-fhqc",
  "modified" : "2025-11-15T03:12:52Z",
  "published" : "2025-11-12T21:27:22Z",
  "aliases" : [ "CVE-2025-64099" ],
  "summary" : "OpenAM: Using arbitrary OIDC requested claims values in id_token and user_info is allowed ",
  "details" : "### Summary\nIf the \"claims_parameter_supported\" parameter is activated, it is possible through the \"oidc-claims-extension.groovy\" script, to inject the value of choice into a claim contained in the id_token or in the user_info.\nAuthorization function requests do not prevent a claims parameter containing a JSON file to be injected. This JSON file allows users to customize claims returned by the \"id_token\" and \"user_info\" files.\nThis 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, users can choose to entera any email address, and therefore assume any chosen identity.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.openidentityplatform.openam:openam-oauth2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "16.0.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-39hr-239p-fhqc"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-64099"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/OpenIdentityPlatform/OpenAM/commit/4254b34b2b8b4867f2e7fccfac73904213d48510"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/OpenIdentityPlatform/OpenAM"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/OpenIdentityPlatform/OpenAM/releases/tag/16.0.3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-74", "CWE-94" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-11-12T21:27:22Z",
    "nvd_published_at" : "2025-11-12T19:15:38Z"
  }
}