Skip to content
Fencer Vulns
low 2.7

CVE-2020-1717 json

Generation of Error Message Containing Sensitive Information in Keycloak

published 2021-02-11 5 y ago modified 2026-06-17 4 mo ago also GHSA-rvfc-g8j5-9ccf , EUVD-2022-1183

cvss
2.7
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 56%
public exploits
0
none known

Summary

A flaw was found in Keycloak 7.0.1. A logged in user can do an account email enumeration attack.

Patch / fix

  • keycloak Arch Linux 16.0.0-1

arch linux advisories AVG-1332

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-1717 updated cvss 2.7

Keycloak: A logged in user can do an account email enumeration attack

  • Red Hat Fuse 7 keycloak keycloak
    affected: no fix available “Fix deferred”
  • Red Hat OpenShift Application Runtimes keycloak keycloak Red Hat Single Sign-On 7 rh-sso7-keycloak rh-sso7-keycloak
    affected: no fix available
  • Red Hat support for Spring Boot keycloak keycloak
    affected: no fix available “Fix deferred”

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

Exploit prediction

0.78% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
maven org.keycloak:keycloak-parent
<=7.0.1
 no fix listed

Affected products

  • n/a keycloak

Classification

Weakness
  • CWE-209 Generation of Error Message Containing Sensitive Information

References

Sources

Fencer Vulns 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.