Skip to content
Fencer Intel
medium 6.5

CVE-2019-3875 json

Improper Certificate Validation and Insufficient Verification of Data Authenticity in Keycloak

published 7y ago modified 4mo ago also GHSA-38cg-gg9j-q9j9 , EUVD-2019-0491

cvss
6.5
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 21%
public exploits
0
none known

Summary

A vulnerability was found in keycloak before 6.0.2. The X.509 authenticator supports the verification of client certificates through the CRL, where the CRL list can be obtained from the URL provided in the certificate itself (CDP) or through the separately configured path. The CRL are often available over the network through unsecured protocols ('http' or 'ldap') and hence the caller should verify the signature and possibly the certification path. Keycloak currently doesn't validate signatures on CRL, which can result in a possibility of various attacks like man-in-the-middle.

Patch / fix

  • redhat keycloak 6.0.2

Is CVE-2019-3875 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-2019-3875 updated cvss 6.5

keycloak: missing signatures validation on CRL used to verify client certificates

  • Red Hat Fuse 7 keycloak keycloak
    affected: no fix planned “Will not fix”
  • Red Hat Mobile Application Platform 4 keycloak Red Hat OpenShift Application Runtimes keycloak keycloak
    affected: no fix planned “Out of support scope”
  • Red Hat Single Sign-On 7 rh-sso7-keycloak rh-sso7-keycloak Red Hat support for Spring Boot keycloak keycloak
    affected: no fix available
  • Red Hat Runtimes Spring Boot 2.1.12
    fixed: vendor fix RHSA-2020:2366
  • Red Hat Single Sign-On 7.3.2 zip
    fixed: vendor fix RHSA-2019:1456
  • Red Hat Text-Only RHOAR
    fixed: vendor fix RHSA-2020:2067

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.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
NVD 3.0 4.8 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/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
GitHub 3.0 4.8 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Affected packages

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

Affected products

  • Red Hat keycloak

Classification

Weakness
  • CWE-345 Insufficient Verification of Data Authenticity
  • CWE-295 Improper Certificate Validation

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.