dbcve.org
KeycloakApplication · Redhat

CVE-2022-4361

MEDIUM · 6.1 CVSS v3.1 Published 2023-07-07
Fix available
A fix is available. Upgrade to 7.6.4 / 21.1.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Patch available

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
Keycloak, an open-source identity and access management solution, has a cross-site scripting (XSS) vulnerability in the SAML or OIDC providers. The vulnerability can allow an attacker to execute malicious scripts by setting the AssertionConsumerServiceURL value or the redirect_uri.

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

A detailed technical summary for this CVE is being prepared.

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:< 21.1.2
Single Sign OnApplication
Affected:>= 7.6, < 7.6.4all versions
Openshift Container PlatformApplication
Affected:= 4.11= 4.12
Openshift Container Platform For Ibm LinuxoneApplication
Affected:= 4.9= 4.10
Openshift Container Platform For PowerApplication
Affected:= 4.9= 4.10

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
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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
Upgrade available Upgrade to 7.6.4 / 21.1.2 or later
Fixed in 7.6.421.1.2
Vendor patch github.com →
Recommended fix High confidence

Keycloak 21.1.2 or Red Hat Single Sign-On 7.6.4

  1. 1. Identify the Keycloak or Single Sign-On version currently deployed in your environment
  2. 2. For standalone Keycloak: Download Keycloak 21.1.2 from the official Keycloak releases page (https://github.com/keycloak/keycloak/releases/tag/21.1.2)
  3. 3. For Red Hat Single Sign-On: Upgrade to version 7.6.4 from your Red Hat subscription management portal
  4. 4. For OpenShift Container Platform: Apply the corresponding CVE fix through your OCP patch management process - for OCP 4.11 and 4.12, this will come via the Keycloak embedded operator update
  5. 5. After upgrading, verify the fix by testing SAML login flows with malicious payloads in AssertionConsumerServiceURL and OIDC flows with malicious redirect_uri values
  6. 6. Ensure input validation is enabled and sanitize any user-supplied URLs used in authentication flows
Caveat Review Keycloak 21.x release notes for any breaking changes from your current version before upgrading

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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