# CVE-2020-10770: Keycloak vulnerable to Server-Side Request Forgery

> Attackers can force Keycloak to request unverified URLs via the request_uri parameter, enabling Server-Side Request Forgery attacks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-jh7q-5mwf-qvhw, RHSA-2021:0318, RHSA-2021:0319, RHSA-2021:0320

## What is CVE-2020-10770?

CVE-2020-10770 is a medium-severity server-side request forgery vulnerability in Redhat Keycloak, published on 15 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in Keycloak before 13.0.0, where it is possible to force the server to call out an unverified URL using the OIDC parameter request_uri. This flaw allows an attacker to use this parameter to execute a Server-side request forgery (SSRF) attack.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2020-10770?

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 | 13.0.0 |
| `org.keycloak:keycloak-core` | Maven | All versions | 13.0.0 |
| `rh-sso7-keycloak` | Red Hat:red_hat_single_sign_on:7::el6 | All versions | 0:9.0.11-1.redhat_00001.1.el6sso |
| `rh-sso7-keycloak-server` | Red Hat:red_hat_single_sign_on:7::el6 | All versions | 0:9.0.11-1.redhat_00001.1.el6sso |
| `rh-sso7-keycloak` | Red Hat:red_hat_single_sign_on:7::el7 | All versions | 0:9.0.11-1.redhat_00001.1.el7sso |
| `rh-sso7-keycloak-server` | Red Hat:red_hat_single_sign_on:7::el7 | All versions | 0:9.0.11-1.redhat_00001.1.el7sso |
| `rh-sso7-keycloak` | Red Hat:red_hat_single_sign_on:7::el8 | All versions | 0:9.0.11-1.redhat_00001.1.el8sso |
| `rh-sso7-keycloak-server` | Red Hat:red_hat_single_sign_on:7::el8 | All versions | 0:9.0.11-1.redhat_00001.1.el8sso |

Products: Redhat Keycloak.

## How do I fix CVE-2020-10770?

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

## Is CVE-2020-10770 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-10770 exists.

Public exploit code:

- Keycloak 12.0.1 - 'request_uri ' Blind Server-Side Request Forgery (SSRF) (Unauthenticated)  (github_poc): https://github.com/ColdFusionX/Keycloak-12.0.1-CVE-2020-10770
- Keycloak Blind SSRF POC (github_poc): https://github.com/0xlyvio/CVE-2020-10770-keycloak-exploit-poc
- Keycloak 12.0.1 - 'request_uri ' Blind Server-Side Request Forgery (SSRF) (Unauthenticated) (exploitdb)
- Keycloak <= 12.0.1 - request_uri Blind Server-Side Request Forgery (SSRF) (nuclei): http/cves/2020/CVE-2020-10770.yaml

## 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-2020-10770 and fix it if it is affected.

What it is: CVE-2020-10770 is a medium-severity server-side request forgery vulnerability in Redhat Keycloak, published on 15 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-10770 exists.

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

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

## Sources

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

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