dbcve.org
KeycloakApplication · Redhat

CVE-2022-2668

HIGH · 7.2 CVSS v3.1 Published 2022-08-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
An issue was discovered in Keycloak that allows arbitrary Javascript to be uploaded for the SAML protocol mapper even if the UPLOAD_SCRIPTS feature is disabled

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

Keycloak allows authenticated administrators to upload arbitrary JavaScript code through SAML protocol mappers, even when the UPLOAD_SCRIPTS feature is explicitly disabled. This represents a security control bypass where the intended protection mechanism fails, potentially allowing remote code execution.

MitigationUpgrade Keycloak to the patched version or disable SAML protocol mapper functionality entirely if the upgrade cannot be performed promptly.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
KeycloakApplication
Affected:= 18.0.0
Single Sign OnApplication
Affected:= 7.0

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

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. Check installed Keycloak version
    Run 'kc.sh --version' or check the server startup logs for the Keycloak version number
    Affected if Version is 18.0.0 for Keycloak or 7.0 for Red Hat Single Sign On
  2. Verify SAML is enabled in your realm
    Inspect the realm settings in the Keycloak admin console or check the realm configuration XML/JSON for the SAML protocol enabled flag
    Affected if SAML protocol is enabled in any realm configuration
  3. Confirm UPLOAD_SCRIPTS feature flag status
    Check the startup parameters or configuration files (standalone.xml, conf/keycloak.conf) for the 'upload-scripts' feature flag setting
    Affected if UPLOAD_SCRIPTS is explicitly set to false or disabled but SAML mappers can still accept script content
  4. Inspect SAML protocol mapper configurations
    Review the SAML protocol mapper definitions in the realm configuration or database table for mapper types that accept JavaScript (javascript-mapper, script-mapper)
    Affected if SAML protocol mappers with JavaScript execution capabilities exist in any realm even when UPLOAD_SCRIPTS is disabled
  5. Test for script upload bypass (if authorized)
    Attempt to create or modify a SAML protocol mapper with JavaScript code through the admin API while UPLOAD_SCRIPTS is disabled
    Affected if JavaScript can be added to a SAML protocol mapper despite the UPLOAD_SCRIPTS feature being disabled

You are affected if you run Keycloak 18.0.0 or RH SSO 7.0 with SAML protocol enabled and SAML mappers can contain JavaScript scripts regardless of the UPLOAD_SCRIPTS feature setting.

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 Keycloak to the patched version or disable SAML protocol mapper functionality entirely if the upgrade cannot be performed promptly.

Recommended fix Moderate confidence

Keycloak 18.0.2 or later (19.x/20.x recommended)

  1. 1. Identify all Keycloak instances running version 18.0.0
  2. 2. Plan upgrade to a stable release that includes the security fix
  3. 3. Before production upgrade, test in a staging environment to verify SAML mapper functionality works correctly
  4. 4. Perform a backup of the current Keycloak configuration
  5. 5. Upgrade Keycloak to version 18.0.2 or later (19.x/20.x recommended for long-term support)
  6. 6. Verify that the UPLOAD_SCRIPTS setting is properly enforced after upgrade
  7. 7. Test SAML single sign-on flows to ensure mappers work as expected
Caveat Review release notes for any breaking changes between 18.0.0 and target upgrade version; major version jumps may include configuration or API changes

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

Fix this in Keycloak Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-2668 — 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-2022-2668 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