Skip to content
Fencer Vulns
critical 9.8

CVE-2017-7474 json

keycloak-connect and keycloak-js improperly handle invalid tokens

published 2017-05-12 9 y ago modified 2026-06-17 4 mo ago also GHSA-mw35-24gh-f82w , EUVD-2017-0349

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.5%
EPSS 2.5% chance of exploitation in 30 days, percentile 85%
public exploits
0
none known

Summary

It was found that the Keycloak Node.js adapter 2.5 - 3.0 did not handle invalid tokens correctly. An attacker could use this flaw to bypass authentication and gain access to restricted information, or to possibly conduct further attacks.

Patch / fix

  • npm keycloak-connect 3.1.0
  • npm keycloak-js 3.1.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-2017-7474 updated cvss 8.1

keycloak-connect: auth token validity check ignored

  • Red Hat Single Sign-On 7 keycloak-connect keycloak-connect
    affected: no fix available
  • Red Hat Single Sign-On 7.1
    fixed: vendor fix RHSA-2017:1203

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

2.54% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
npm keycloak-connect
>=2.5.0, <3.1.0
3.1.0
npm keycloak-js
>=2.5.0, <3.1.0
3.1.0

Affected products

  • Red Hat, Inc. Keycloak Node.js adapter

Classification

Weakness
  • CWE-253 Incorrect Check of Function Return Value

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.