Approved changes feed: RSS · Atom

cpe:2.3:a:red_hat,_inc.:keycloak:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorRed Hat, Inc. (955c0640-1cfb-5fef-a58d-675724883b3d)
ProductKeycloak (294db9aa-6e83-5819-9a51-b450e2ae18ad)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2017-2585 vulnerable 2026-06-03 14:37:07.748397 Details available
Red Hat Keycloak before version 2.5.1 has an implementation of HMAC verification for JWS tokens that uses a method that runs in non-constant time, potentially leaving the application vulnerable to timing attacks.
Published: 2018-03-12T15:00:00.000Z
Updated: 2024-09-16T22:56:17.924Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2017-12161 vulnerable 2026-06-03 14:36:34.474701 Details available
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.
Published: 2018-02-21T18:00:00.000Z
Updated: 2024-08-05T18:28:16.559Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2017-12160 vulnerable 2026-06-03 14:36:34.472273 Details available
It was found that Keycloak oauth would permit an authenticated resource to obtain an access/refresh token pair from the authentication server, permitting indefinite usage in the case of permission revocation. An attacker on an already compromised resource could use this flaw to grant himself continued permissions and possibly conduct further attacks.
Published: 2017-10-26T17:00:00.000Z
Updated: 2024-09-16T18:48:51.709Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2017-12159 vulnerable 2026-06-03 14:36:34.471675 Details available
It was found that the cookie used for CSRF prevention in Keycloak was not unique to each session. An attacker could use this flaw to gain access to an authenticated user session, leading to possible information disclosure or further attacks.
Published: 2017-10-26T17:00:00.000Z
Updated: 2024-09-16T21:02:35.248Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2017-12158 vulnerable 2026-06-03 14:36:34.467004 Details available
It was found that Keycloak would accept a HOST header URL in the admin console and use it to determine web resource locations. An attacker could use this flaw against an authenticated user to attain reflected XSS via a malicious server.
Published: 2017-10-26T17:00:00.000Z
Updated: 2024-09-16T23:36:41.599Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2016-8629 vulnerable 2026-06-03 14:36:09.662143 Details available
Red Hat Keycloak before version 2.4.0 did not correctly check permissions when handling service account user deletion requests sent to the rest server. An attacker with service account authentication could use this flaw to bypass normal permissions and delete users in a separate realm.
Published: 2018-03-12T15:00:00.000Z
Updated: 2024-09-16T17:52:54.232Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.