CVE-2020-1728 json
Improper Restriction of Rendered UI Layers or Frames in Keycloak
published 6y ago modified 4mo ago also GHSA-3gg7-9q2x-79fc , EUVD-2020-0360
- cvss
- 4.8
- version 3.1, CNA
- 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 vulnerability was found in all versions of Keycloak where, the pages on the Admin Console area of the application are completely missing general HTTP security headers in HTTP-responses. This does not directly lead to a security issue, yet it might aid attackers in their efforts to exploit other problems. The flaws unnecessarily make the servers more prone to Clickjacking, channel downgrade attacks and other similar client-based attack vectors.
Patch / fix
- redhat keycloak 10.0.0
- rh-sso7-keycloak red hat single sign on 7 9.0.5-1.redhat_00001.1.el8sso
- rh-sso7-keycloak-server red hat single sign on 7 9.0.5-1.redhat_00001.1.el8sso
- rh-sso7-keycloak red hat single sign on 7 9.0.5-1.redhat_00001.1.el7sso
- rh-sso7-keycloak-server red hat single sign on 7 9.0.5-1.redhat_00001.1.el7sso
- rh-sso7-keycloak red hat single sign on 7 9.0.5-1.redhat_00001.1.el6sso
- rh-sso7-keycloak-server red hat single sign on 7 9.0.5-1.redhat_00001.1.el6sso
red hat advisories RHSA-2020:3497RHSA-2020:3496RHSA-2020:3495
Is CVE-2020-1728 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-1728 updated cvss 4.8
keycloak: security headers missing on REST endpoints
-
Red Hat build of Quarkus keycloak keycloakaffected: no fix available
-
Red Hat OpenShift Application Runtimes keycloak keycloakaffected: no fix planned “Out of support scope”
-
Red Hat support for Spring Boot keycloak keycloakaffected: no fix available
-
Red Hat build of Quarkus 1.7.5fixed: vendor fix RHSA-2020:4252
-
Red Hat Runtimes Spring Boot 2.2.10fixed: vendor fix RHSA-2020:4213
-
Red Hat Single Sign-On 7.4 for RHEL 6 Server rh-sso7-keycloak 9.0.5-1.redhat_00001.1.el6sso, rh-sso7-keycloak-server 9.0.5-1.redhat_00001.1.el6ssofixed: vendor fix RHSA-2020:3495
-
Red Hat Single Sign-On 7.4 for RHEL 7 Server rh-sso7-keycloak 9.0.5-1.redhat_00001.1.el7sso, rh-sso7-keycloak-server 9.0.5-1.redhat_00001.1.el7ssofixed: vendor fix RHSA-2020:3496
-
Red Hat Single Sign-On 7.4 for RHEL 8 rh-sso7-keycloak 9.0.5-1.redhat_00001.1.el8sso, rh-sso7-keycloak-server 9.0.5-1.redhat_00001.1.el8ssofixed: vendor fix RHSA-2020:3497
show 3 moreshow fewer
-
Red Hat Single Sign-On 7.4.2fixed: vendor fix RHSA-2020:3501
-
Red Hat Text-Only RHOARfixed: vendor fix RHSA-2020:3539
-
Red Hat Fuse 7 keycloak keycloaknot 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.78% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N |
| NVD | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N |
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:P/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.keycloak:keycloak-core | <=9.0.3 |
no fix listed |
Affected products
- [UNKNOWN] keycloak
Classification
References
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2020-1728
web, issue-tracking, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-1728
advisory
-
issues.redhat.com
/browse/KEYCLOAK-12264
web
Sources
- CVE List CVE-2020-1728
- GitHub Advisory GHSA-3gg7-9q2x-79fc
- NVD CVE-2020-1728
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.