dbcve.org
InjectionWeakness · CWE-74

CVE-2025-64099

HIGH · 8.1 CVSS v4.0 Published 2025-11-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OpenAM versions prior to 16.0.0 contain an OIDC claims injection vulnerability when claims_parameter_supported is enabled. Attackers can inject malicious JSON via the claims parameter in an authorize request to manipulate the oidc-claims-extension.groovy script, allowing arbitrary modification of claims in id_token and user_info responses. This enables identity spoofing if clients rely on claim values like email for authentication.

MitigationUpgrade to OpenAM version 16.0.0 or later. Alternatively, disable the claims_parameter_supported configuration until patching is feasible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenAM version
    Retrieve the installed OpenAM version from the system or admin console and compare it to 16.0.0
    Affected if The installed version is prior to 16.0.0
  2. Verify OIDC claims parameter support
    Locate the OpenAM OIDC provider configuration and check whether the claims_parameter_supported setting is enabled
    Affected if claims_parameter_supported is set to true or enabled
  3. Inspect oidc-claims-extension.groovy script
    Find and examine the oidc-claims-extension.groovy script used for OIDC claims customization for any unauthorized modifications or unexpected content
    Affected if The script contains injected or unexpected JSON/claims data not authored by administrators
  4. Review id_token and user_info claims
    Query id_token and user_info endpoints for a test user and inspect the returned claims, particularly sensitive claims like email
    Affected if Claims values differ from expected values or contain injected data
  5. Audit OIDC authorize request logs
    Search authentication logs for authorize requests containing the claims parameter and inspect for abnormal or injection patterns
    Affected if There are authorize requests with claims parameter values that include unexpected JSON structures

You are affected if OpenAM version is prior to 16.0.0 AND claims_parameter_supported is enabled, regardless of whether external tampering is yet observable in logs or tokens

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to OpenAM version 16.0.0 or later. Alternatively, disable the claims_parameter_supported configuration until patching is feasible.

Recommended fix High confidence

OpenAM version 16.0.0

  1. 1. Identify all OpenAM deployments currently running versions prior to 16.0.0
  2. 2. Verify if the 'claims_parameter_supported' parameter is enabled in your OpenID Connect configuration
  3. 3. Schedule a maintenance window for the upgrade
  4. 4. Backup the current OpenAM configuration and database
  5. 5. Upgrade OpenAM to version 16.0.0 or later
  6. 6. After upgrade, verify that the 'claims_parameter_supported' functionality works correctly with proper input validation
  7. 7. Test that legitimate OIDC authorization flows with claims parameter function as expected
  8. 8. Monitor logs for any attempts to exploit the injection vulnerability

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64099 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-64099 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data