Skip to content
Fencer Intel
medium 5.4

CVE-2020-1725 json

Incorrect Authorization in keycloak

published 5y ago modified 4mo ago also GHSA-p225-pc2x-4jpm , EUVD-2022-1113

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

Summary

A flaw was found in keycloak before version 13.0.0. In some scenarios a user still has access to a resource after changing the role mappings in Keycloak and after expiration of the previous access token.

Patch / fix

  • maven org.keycloak:keycloak-parent 13.0.0
  • redhat keycloak 13.0.0
  • keycloak Arch Linux 16.0.0-1

arch linux advisories AVG-1332

Is CVE-2020-1725 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-1725 updated cvss 5.4

keycloak-gatekeeper: improper usage of parsed claims for authorization leads to improper resource access

  • Red Hat Fuse 7 keycloak keycloak Red Hat Mobile Application Platform 4 keycloak Red Hat OpenShift Application Runtimes keycloak keycloak Red Hat Single Sign-On 7 rh-sso7-keycloak rh-sso7-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

Exploit prediction

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

CVSS scores

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

Affected packages

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

Affected products

  • n/a keycloak

Classification

Weakness
  • CWE-863 Incorrect Authorization
  • CWE-668 Exposure of Resource to Wrong Sphere

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.