# CVE-2017-2646: Keycloak vulnerable to infinite loop based Denial of Service

> An attacker can cause a denial of service in Keycloak by sending a malformed SAML logout request that triggers an infinite loop.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jc6q-27mw-p55w

## What is CVE-2017-2646?

CVE-2017-2646 is a high-severity denial of service vulnerability in Redhat Keycloak, published on 27 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

It was found that when Keycloak before 2.5.5 receives a Logout request with a Extensions in the middle of the request, the SAMLSloRequestParser.parse() method ends in a infinite loop. An attacker could use this flaw to conduct denial of service attacks.

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

## Which versions are affected by CVE-2017-2646?

2 open source packages ship an affected version, including org.keycloak:keycloak-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-core` | Maven | All versions | 2.5.5 |
| `org.keycloak:keycloak-core` | Maven | All versions | 2.5.5 |

Products: Redhat Keycloak.

## How do I fix CVE-2017-2646?

Upgrade org.keycloak:keycloak-core to 2.5.5 or later.

## Is CVE-2017-2646 being exploited?

There is no known exploitation of CVE-2017-2646 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Keycloak

- [CVE-2022-4361](https://insights.sbomify.com/CVE-2022-4361/): Keycloak vulnerable to cross-site scripting when validating URI-schemes on SAML and OIDC (critical 10.0)
- [CVE-2022-1245](https://insights.sbomify.com/CVE-2022-1245/): Keycloak vulnerable to privilege escalation on Token Exchange feature (critical 9.8)
- [CVE-2021-20195](https://insights.sbomify.com/CVE-2021-20195/): keycloak Self Stored Cross-site Scripting vulnerability (critical 9.6)
- [CVE-2019-14910](https://insights.sbomify.com/CVE-2019-14910/): Keycloak Authentication Error (critical 9.3)
- [CVE-2019-14909](https://insights.sbomify.com/CVE-2019-14909/): Keycloak Authentication Error (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-2646 and fix it if it is affected.

What it is: CVE-2017-2646 is a high-severity denial of service vulnerability in Redhat Keycloak, published on 27 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-2646 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-core (Maven): affected all versions; fixed in 2.5.5
- org.keycloak:keycloak-core (Maven): affected all versions; fixed in 2.5.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-2646/ (Markdown: https://insights.sbomify.com/CVE-2017-2646/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-2646
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-2646
- OSV: https://osv.dev/vulnerability/CVE-2017-2646

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-2646/
Summaries are generated and may contain mistakes; the official description above is the record.