Skip to content

GHSA-qc72-gfvw-76h7 CVE-2017-12160

Keycloak Oauth Implementation Error

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

Description

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.

Affected versions

Maven

PackageVulnerableFixed in
org.keycloak:keycloak-parent
< 3.3.0.Final
3.3.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 → 3.3.0.Final

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

Severity breakdown

CVSS 3.1 7.2

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

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

Weakness

CWE-287: Improper Authentication

When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

How to prevent it
  • Architecture and Design: Use an authentication framework or library such as the OWASP ESAPI Authentication feature.

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