CVE-2020-1698 json
Keycloak leaks sensitive information in logged exceptions
published 6y ago modified 4mo ago also GHSA-qgmm-f2qw-r95f , EUVD-2022-4970
- cvss
- 5.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 31%
- public exploits
- 0
- none known
Summary
A flaw was found in keycloak in versions before 9.0.0. A logged exception in the HttpMethod class may leak the password given as parameter. The highest threat from this vulnerability is to data confidentiality.
Patch / fix
- maven org.keycloak:keycloak-core 9.0.0
- redhat keycloak 9.0.0
- github.com/keycloak/keycloak@62c9e15 commit
- github.com/keycloak/keycloak#6751 pull request
Is CVE-2020-1698 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 FencerVendor 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-1698 updated cvss 5.0
keycloak: Password leak by logged exception in HttpMethod class
-
Red Hat Fuse 7 keycloak-coreaffected: no fix available “Fix deferred”
-
Red Hat Mobile Application Platform 4 keycloak-coreaffected: no fix planned “Out of support scope”
-
Red Hat OpenShift Application Runtimes keycloak-core Red Hat Single Sign-On 7 rh-sso7-keycloak rh-sso7-keycloak Red Hat support for Spring Boot keycloak-coreaffected: no fix available
-
Red Hat Runtimes Spring Boot 2.2.6fixed: vendor fix RHSA-2020:2252
-
Red Hat Single Sign-On 7.4.0fixed: vendor fix RHSA-2020:5625
-
Red Hat Text-Only RHOARfixed: vendor fix RHSA-2020:2905
-
Red Hat Decision Manager 7 keycloak-core Red Hat Process Automation 7 keycloak-corenot 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
Exploit prediction
0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.0 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.keycloak:keycloak-core | <9.0.0 |
9.0.0 |
Affected products
- Red Hat keycloak
Classification
References
-
github.com
/keycloak/keycloak/pull/6751
web
-
github.com
/keycloak/keycloak/commit/62c9e1577618470832ede22dcedd46cba15b1836
web
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2020-1698
web, issue-tracking, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-1698
advisory
Sources
- CVE List CVE-2020-1698
- GitHub Advisory GHSA-qgmm-f2qw-r95f
- NVD CVE-2020-1698
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.