Skip to content
Fencer Vulns
high 8.1

CVE-2019-10201 json

Improper Verification of Cryptographic Signature in keycloak

published 2019-08-14 7 y ago modified 2026-06-17 4 mo ago also GHSA-4fgq-gq9g-3rw7 , EUVD-2019-0650

cvss
8.1
version 3.0, CNA
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

It was found that Keycloak's SAML broker, versions up to 6.0.1, did not verify missing message signatures. If an attacker modifies the SAML Response and removes the <Signature> sections, the message is still accepted, and the message can be modified. An attacker could use this flaw to impersonate other users and gain access to sensitive information.

Patch / fix

  • maven org.keycloak:keycloak-core 7.0.0

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-2019-10201 updated cvss 8.1

keycloak: SAML broker does not check existence of signature on document allowing any user impersonation

  • Red Hat Fuse 7 keycloak keycloak
    affected: workaround, no fix planned “Administrator can prevent this issue for POST binding by requiring signed assertions.”
  • Red Hat OpenShift Application Runtimes keycloak keycloak Red Hat Single Sign-On 7 rh-sso7-keycloak rh-sso7-keycloak
    affected: workaround, no fix available “Administrator can prevent this issue for POST binding by requiring signed assertions.”
  • Red Hat Runtimes Spring Boot 2.1.12
    fixed: vendor fix “Administrator can prevent this issue for POST binding by requiring signed assertions.” RHSA-2020:2366
  • Red Hat Single Sign-On 7.3.3 zip
    fixed: vendor fix “Administrator can prevent this issue for POST binding by requiring signed assertions.” RHSA-2019:2483
  • Red Hat Text-Only RHOAR
    fixed: vendor fix “Administrator can prevent this issue for POST binding by requiring signed assertions.” RHSA-2020:2067
  • Red Hat Mobile Application Platform 4 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.71% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Affected packages

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

Affected products

  • Red Hat keycloak

Classification

Weakness
  • CWE-592 DEPRECATED: Authentication Bypass Issues
  • CWE-347 Improper Verification of Cryptographic Signature

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.