# CVE-2018-14655: Keycloak vulnerable to cross-site scripting via the state parameter

> Attackers can inject JavaScript via the state parameter in authentication URLs, leading to XSS and potential account takeover.

- **Severity:** Medium 4.6 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-458h-wv48-fq75

## What is CVE-2018-14655?

CVE-2018-14655 is a medium-severity cross-site scripting vulnerability in Redhat Keycloak, published on 13 Nov 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A flaw was found in Keycloak 3.4.3.Final, 4.0.0.Beta2, 4.3.0.Final. When using 'response_mode=form_post' it is possible to inject arbitrary Javascript-Code via the 'state'-parameter in the authentication URL. This allows an XSS-Attack upon succesfully login.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2018-14655?

6 open source packages ship an affected version, including org.keycloak:keycloak-parent. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-parent` | Maven | All versions | None |
| `org.keycloak:keycloak-parent` | Maven | All versions | None |
| `org.keycloak:keycloak-parent` | Maven | All versions to 3.4.3.Final | None |
| `org.keycloak:keycloak-parent` | Maven | All versions to 3.4.3.Final | None |
| `org.keycloak:keycloak-parent` | Maven | From 4.0.0.Beta1 to 4.0.0.Beta2 | None |
| `org.keycloak:keycloak-parent` | Maven | From 4.0.0.Beta1 to 4.0.0.Beta2 | None |

Products: Redhat Keycloak, Redhat Single Sign-On.

## How do I fix CVE-2018-14655?

Upgrade to a fixed version.

## Is CVE-2018-14655 being exploited?

There is no known exploitation of CVE-2018-14655 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-2018-14655 and fix it if it is affected.

What it is: CVE-2018-14655 is a medium-severity cross-site scripting vulnerability in Redhat Keycloak, published on 13 Nov 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-14655 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-parent (Maven): affected all versions; no fix listed
- org.keycloak:keycloak-parent (Maven): affected all versions; no fix listed
- org.keycloak:keycloak-parent (Maven): affected all versions up to 3.4.3.Final; no fix listed
- org.keycloak:keycloak-parent (Maven): affected all versions up to 3.4.3.Final; no fix listed
- org.keycloak:keycloak-parent (Maven): affected from 4.0.0.Beta1 up to 4.0.0.Beta2; no fix listed
- org.keycloak:keycloak-parent (Maven): affected from 4.0.0.Beta1 up to 4.0.0.Beta2; no fix listed

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-2018-14655/ (Markdown: https://insights.sbomify.com/CVE-2018-14655/index.md)
```

## Sources

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

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