CVE-2022-0225: Keycloak XSS via use of malicious payload as group name when creating new group from admin console

CVE-2022-0225 · Severity: low · CVSS 3.1 · Published 2022-08-27

Keycloak XSS via use of malicious payload as group name when creating new group from admin console

Technologies: org.keycloak:keycloak-core (Maven). Vendors: Maven.

Quick answers

Is CVE-2022-0225 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-0225 being exploited in the wild.
How severe is CVE-2022-0225?
Low severity, with a CVSS score of 3.1, published 27 August 2022.
Which products and versions are affected?
org.keycloak:keycloak-core (Maven) ECOSYSTEM:introduced=0,fixed=20.0.0, ECOSYSTEM:introduced=0,last_affected=16.1.0.
Is there a fix for CVE-2022-0225?
Yes. org.keycloak:keycloak-core (Maven): upgrade to 20.0.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-0225?
Check whether you run org.keycloak:keycloak-core (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.keycloak:keycloak-core (Maven): upgrade to 20.0.0 or later
    # set org.keycloak:keycloak-core to 20.0.0 in your pom.xml or build.gradle

Affected products

  • org.keycloak:keycloak-core (Maven) ECOSYSTEM:introduced=0,fixed=20.0.0, ECOSYSTEM:introduced=0,last_affected=16.1.0

Identifiers

  • CVE-2022-0225
  • GHSA-755v-r4x4-qf7m
  • GHSA-fqc7-5xxc-ph7r

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.