WaratekVRT Sign in

Org.keycloak CVEs

206 CVEs, 3 exploited, 8 protected by Waratek

Reset
More filters (1)
Columns
Vendor org.keycloak✕
Overview 206 matches · 8 protected · 3 exploited · 0 CISA KEV · 9 public PoC · 1 EPSS ≥ 0.5
split by peak 69 / year
No exploit published: 189Mitigation candidate: 9Protected by Waratek: 8 Low: 23Medium: 106High: 69Critical: 8 not blocked: 198blocked by ARMR today: 8 No public exploit: 195Proof of concept only: 4Working exploit published: 4Exploited: 3
2017201820192020202120222023202420252026
206 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed. ‹ prev page 3 of 3 next ›
CVE Severity Published▾ Status Exploitation Description
CVE-2017-12161 High 2018-02-21 No exploit published No public exploit 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.
CVE-2014-3651 High 2017-12-29 No exploit published No public exploit JBoss KeyCloak before 1.0.3.Final allows remote attackers to cause a denial of service (resource consumption) via a large value in the size parameter to auth/qrcode, related to QR code generation.
CVE-2017-12160 High 2017-10-26 No exploit published No public exploit 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.
CVE-2017-12159 High 2017-10-26 No exploit published No public exploit 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.
CVE-2017-12158 Medium 2017-10-26 No exploit published No public exploit 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.
CVE-2014-3709 High 2017-10-18 No exploit published No public exploit The org.keycloak.services.resources.SocialResource.callback method in JBoss KeyCloak before 1.0.3.Final allows remote attackers to conduct cross-site request forgery (CSRF) attacks by leveraging lack of CSRF protection.
‹ prev page 3 of 3 next ›