Skip to content
Fencer Intel
medium 6.1

CVE-2018-14637 json

Improper Authentication in Keycloak

published 7y ago modified 4mo ago also GHSA-gf2j-7qwg-4f5x , EUVD-2018-0810

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

Summary

The SAML broker consumer endpoint in Keycloak before version 4.6.0.Final ignores expiration conditions on SAML assertions. An attacker can exploit this vulnerability to perform a replay attack.

Patch / fix

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

red hat advisories RHSA-2018:3593RHSA-2018:3592

Is CVE-2018-14637 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-2018-14637 updated cvss 6.1

keycloak: expiration not validated in SAML broker consumer endpoint

  • Red Hat Mobile Application Platform 4 keycloak
    affected: no fix planned “Out of support scope”
  • Red Hat Single Sign-On 7.2 for RHEL 6 Server rh-sso7-keycloak 3.4.14-1.Final_redhat_00001.1.jbcs.el6, rh-sso7-keycloak-server 3.4.14-1.Final_redhat_00001.1.jbcs.el6
    fixed: vendor fix RHSA-2018:3592
  • Red Hat Single Sign-On 7.2 for RHEL 7 Server rh-sso7-keycloak 3.4.14-1.Final_redhat_00001.1.jbcs.el7, rh-sso7-keycloak-server 3.4.14-1.Final_redhat_00001.1.jbcs.el7
    fixed: vendor fix RHSA-2018:3593
  • Red Hat Single Sign-On 7.2.5 zip
    fixed: vendor fix RHSA-2018:3595
  • Red Hat Fuse 7 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

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

CVSS scores

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

Affected packages

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

Affected products

  • [UNKNOWN] keycloak

Classification

Weakness

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.