Skip to content
Fencer Vulns
high 8.8

CVE-2017-12161 json

Moderate severity vulnerability that affects org.keycloak:keycloak-core

published 2018-02-21 8 y ago modified 2026-06-17 4 mo ago also GHSA-959q-32g8-vvp7 , EUVD-2018-0558

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

Summary

It was found that keycloak before 3.4.2 final would permit misuse of a client-side /etc/hosts entry to spoof a URL in a password reset request. An attacker could use this flaw to craft a malicious password reset request and gain a valid reset token, leading to information disclosure or further attacks.

Patch / fix

  • maven org.keycloak:keycloak-core 3.4.2
  • keycloak keycloak 3.4.2

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-12161 updated cvss 4.2

keycloak: reset password token disclosure

  • Red Hat Mobile Application Platform 4 keycloak
    affected: no fix planned “Will not fix”
  • Red Hat Single Sign-On 7 rh-sso7-keycloak rh-sso7-keycloak
    affected: no fix available

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

CVSS scores

assigned by version score vector
NVD 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N

Affected packages

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

Affected products

  • Red Hat, Inc. Keycloak

Classification

Weakness
  • CWE-602 Client-Side Enforcement of Server-Side Security
  • CWE-640 Weak Password Recovery Mechanism for Forgotten Password

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.