Skip to content

GHSA-85v8-vx4w-q684 CVE-2018-14657

Keycloak Improper Bruteforce Detection

High Maven
Severity
8.1 / 10
High · CVSS 3.1
Exploit chance (EPSS)
1.16%
Chance of exploitation in the next 30 days. Higher than 67.11% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-307 Improper Restriction of Excessive Authentication Attempts
Fix
4.6.0.Final
Upgrade org.keycloak:keycloak-parent to this version or later

Description

A flaw was found in Keycloak 4.2.1.Final, 4.3.0.Final. When TOPT enabled, an improper implementation of the Brute Force detection algorithm will not enforce its protection measures.

Affected versions

Maven

PackageVulnerableFixed in
org.keycloak:keycloak-parent
< 4.6.0.Final
4.6.0.Final

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.keycloak:keycloak-parent Maven → 4.6.0.Final

maven
<dependency><groupId>org.keycloak</groupId><artifactId>keycloak-parent</artifactId><version>4.6.0.Final</version></dependency>
gradle
implementation("org.keycloak:keycloak-parent:4.6.0.Final")

Severity breakdown

CVSS 3.1 8.1

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-307: Improper Restriction of Excessive Authentication Attempts

The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame.

How to prevent it
  • Architecture and Design: Common protection mechanisms include: Disconnecting the user after a small number of failed attempts Implementing a timeout Locking out a targeted account Requiring a computational task on the user's part.
  • Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. Consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator. [REF-45]

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-fwhw-chw4-gh37
Keycloak Server-Side Request Forgery (SSRF) vulnerability
Low Also affects org.keycloak:keycloak-parent
GHSA-gv94-wp4h-vv8p
Keycloak has Incorrect Behavior Order: Authorization Before Parsing and Canonicalization
Medium Also affects org.keycloak:keycloak-parent
GHSA-9hhc-pj4w-w5rv
Keycloak Cross-site Scripting on OpenID connect login service
Medium Also affects org.keycloak:keycloak-parent
GHSA-g8q8-fggx-9r3q
Keycloak vulnerable to path traversal via double URL encoding
Critical Also affects org.keycloak:keycloak-parent
GHSA-97g8-xfvw-q4hg
Keycloak vulnerable to session takeover with OIDC offline refreshtokens
Medium Also affects org.keycloak:keycloak-parent
GHSA-w9mf-83w3-fv49
Keycloak vulnerable to Stored Cross site Scripting (XSS) when loading default roles
Medium Also affects org.keycloak:keycloak-parent
GHSA-wf7g-7h6h-678v
Keycloak SAML javascript protocol mapper: Uploading of scripts through admin console
High Also affects org.keycloak:keycloak-parent
GHSA-xv7h-95r7-595j
Incorrect implementation of lockout feature in Keycloak
High Also affects org.keycloak:keycloak-parent
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor