Skip to content
Fencer Intel
low 3.8

CVE-2019-3868 json

Exposure of Sensitive Information to an Unauthorized Actor in Keycloak

published 7y ago modified 4mo ago also GHSA-gc52-xj6p-9pxp , EUVD-2019-0420

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

Summary

Keycloak up to version 6.0.0 allows the end user token (access or id token JWT) to be used as the session cookie for browser sessions for OIDC. As a result an attacker with access to service provider backend could hijack user’s browser session.

Patch / fix

  • maven org.keycloak:keycloak-core 6.0.0
  • rh-sso7-keycloak red hat single sign on 7 3.4.17-1.Final_redhat_00001.1.jbcs.el7
  • rh-sso7-keycloak-server red hat single sign on 7 3.4.17-1.Final_redhat_00001.1.jbcs.el7
  • rh-sso7-keycloak red hat single sign on 7 3.4.17-1.Final_redhat_00001.1.jbcs.el6
  • rh-sso7-keycloak-server red hat single sign on 7 3.4.17-1.Final_redhat_00001.1.jbcs.el6

red hat advisories RHSA-2019:0856RHSA-2019:0857

Is CVE-2019-3868 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-3868 updated cvss 3.8

keycloak: session hijack using the user access token

  • Red Hat Fuse 7 keycloak keycloak
    affected: no fix planned “Will not fix”
  • Red Hat Mobile Application Platform 4 keycloak
    affected: no fix planned “Out of support scope”
  • Red Hat OpenShift Application Runtimes keycloak 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.2 for RHEL 6 Server rh-sso7-keycloak 3.4.17-1.Final_redhat_00001.1.jbcs.el6, rh-sso7-keycloak-server 3.4.17-1.Final_redhat_00001.1.jbcs.el6
    fixed: vendor fix RHSA-2019:0857
  • Red Hat Single Sign-On 7.2 for RHEL 7 Server rh-sso7-keycloak 3.4.17-1.Final_redhat_00001.1.jbcs.el7, rh-sso7-keycloak-server 3.4.17-1.Final_redhat_00001.1.jbcs.el7
    fixed: vendor fix RHSA-2019:0856
  • Red Hat Single Sign-On 7.2.7 zip
    fixed: vendor fix RHSA-2019:0868
  • Red Hat Single Sign-On 7.3.1 zip
    fixed: vendor fix RHSA-2019:1140
show 2 more
  • Red Hat Text-Only RHOAR
    fixed: vendor fix RHSA-2019:2998
  • Red Hat streams for Apache Kafka keycloak 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

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

CVSS scores

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

Affected packages

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

Affected products

  • Red Hat keycloak

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

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.