Skip to content
Fencer Intel
medium 5.3

CVE-2020-10770 json

Keycloak vulnerable to Server-Side Request Forgery

published 5y ago modified 4mo ago also GHSA-jh7q-5mwf-qvhw , EUVD-2022-4372

cvss
5.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
69.7%
EPSS 69.7% chance of exploitation in 30 days, percentile 99.3%
public exploits
1
Exploit-DB, plus a Nuclei check

Summary

A flaw was found in Keycloak before 13.0.0, where it is possible to force the server to call out an unverified URL using the OIDC parameter request_uri. This flaw allows an attacker to use this parameter to execute a Server-side request forgery (SSRF) attack.

Patch / fix

  • maven org.keycloak:keycloak-core 13.0.0
  • redhat keycloak 12.0.2
  • rh-sso7-keycloak red hat single sign on 7 9.0.11-1.redhat_00001.1.el8sso
  • rh-sso7-keycloak-server red hat single sign on 7 9.0.11-1.redhat_00001.1.el8sso
  • rh-sso7-keycloak red hat single sign on 7 9.0.11-1.redhat_00001.1.el7sso
  • rh-sso7-keycloak-server red hat single sign on 7 9.0.11-1.redhat_00001.1.el7sso
  • rh-sso7-keycloak red hat single sign on 7 9.0.11-1.redhat_00001.1.el6sso
  • rh-sso7-keycloak-server red hat single sign on 7 9.0.11-1.redhat_00001.1.el6sso

red hat advisories RHSA-2021:0320RHSA-2021:0319RHSA-2021:0318

  • keycloak Arch Linux 12.0.2-1

arch linux advisories AVG-1577

Is CVE-2020-10770 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-10770 updated cvss 5.8

keycloak: Default Client configuration is vulnerable to SSRF using "request_uri" parameter

  • Red Hat Single Sign-On 7.4 for RHEL 6 Server rh-sso7-keycloak 9.0.11-1.redhat_00001.1.el6sso, rh-sso7-keycloak-server 9.0.11-1.redhat_00001.1.el6sso
    fixed: vendor fix RHSA-2021:0318
  • Red Hat Single Sign-On 7.4 for RHEL 7 Server rh-sso7-keycloak 9.0.11-1.redhat_00001.1.el7sso, rh-sso7-keycloak-server 9.0.11-1.redhat_00001.1.el7sso
    fixed: vendor fix RHSA-2021:0319
  • Red Hat Single Sign-On 7.4 for RHEL 8 rh-sso7-keycloak 9.0.11-1.redhat_00001.1.el8sso, rh-sso7-keycloak-server 9.0.11-1.redhat_00001.1.el8sso
    fixed: vendor fix RHSA-2021:0320
  • Red Hat Single Sign-On 7.4.5
    fixed: vendor fix RHSA-2021:0327
  • Red Hat Decision Manager 7 keycloak keycloak Red Hat Fuse 7 keycloak keycloak Red Hat OpenShift Application Runtimes keycloak keycloak Red Hat Process Automation 7 keycloak keycloak Red Hat support for Spring Boot keycloak keycloak
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. Published
  2. First public exploit (EDB-50405)

Exploit prediction

69.72% chance of exploitation in the next 30 days, higher than 99.3% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-50405 Keycloak 12.0.1 - 'request_uri ' Blind Server-Side Request Forgery (SSRF) (Unauthenticated) webapps, 2021-10-13
  • Nuclei template Keycloak <= 12.0.1 - request_uri Blind Server-Side Request Forgery (SSRF) nuclei detection template
  • packetstormsecurity.com http://packetstormsecurity.com/files/164499/Keycloak-12.0.1-Server-Side-Request-Forgery.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
maven org.keycloak:keycloak-core
<13.0.0
13.0.0

Affected products

  • n/a keycloak

Classification

Weakness
  • CWE-918 Server-Side Request Forgery
  • CWE-601 URL Redirection to Untrusted Site

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.