Skip to content

Keycloak vulnerable to infinite loop based Denial of Service

High severity GitHub Reviewed Published Oct 18, 2018 to the GitHub Advisory Database • Updated Jan 8, 2023

Package

maven org.keycloak:keycloak-core (Maven)

Affected versions

< 2.5.5

Patched versions

2.5.5

Description

When Keycloak versions prior to 2.5.5 receive a Logout request with an Extensions in the middle of the request, the SAMLSloRequestParser.parse() method ends in an infinite loop. An attacker could use this flaw to conduct denial of service attacks.

References

Published to the GitHub Advisory Database Oct 18, 2018
Reviewed Jun 16, 2020
Last updated Jan 8, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

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

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.085%
(37th percentile)

Weaknesses

CVE ID

CVE-2017-2646

GHSA ID

GHSA-jc6q-27mw-p55w

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.