# CVE-2019-10201: Improper Verification of Cryptographic Signature in keycloak

> Attackers can bypass SAML signature verification to impersonate users and access sensitive information in Keycloak.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Aug 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4fgq-gq9g-3rw7

## What is CVE-2019-10201?

CVE-2019-10201 is a high-severity authentication bypass vulnerability in Redhat Keycloak, published on 14 Aug 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

It was found that Keycloak's SAML broker, versions up to 6.0.1, did not verify missing message signatures. If an attacker modifies the SAML Response and removes the <Signature> sections, the message is still accepted, and the message can be modified. An attacker could use this flaw to impersonate other users and gain access to sensitive information.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature), CWE-592 (DEPRECATED: Authentication Bypass Issues)

## Which versions are affected by CVE-2019-10201?

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


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

Products: Redhat Keycloak, Redhat Single Sign-On.

## How do I fix CVE-2019-10201?

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

## Is CVE-2019-10201 being exploited?

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

What it is: CVE-2019-10201 is a high-severity authentication bypass vulnerability in Redhat Keycloak, published on 14 Aug 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-10201 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-core (Maven): affected all versions; fixed in 7.0.0
- org.keycloak:keycloak-core (Maven): affected all versions; fixed in 7.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-2019-10201/ (Markdown: https://insights.sbomify.com/CVE-2019-10201/index.md)
```

## Sources

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

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