# CVE-2019-14832: Keycloak Unauthenticated Access

> An authenticated attacker can access unauthorized user information from other realms via the Keycloak REST API.

- **Severity:** Medium 5.0 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 15 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8prc-58j4-m55q

## What is CVE-2019-14832?

CVE-2019-14832 is a medium-severity missing authorization vulnerability in Redhat Keycloak, published on 15 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in the Keycloak REST API before version 8.0.0 where it would permit user access from a realm the user was not configured. An authenticated attacker with knowledge of a user id could use this flaw to access unauthorized information or to carry out further attacks.

Weakness: CWE-863 (Incorrect Authorization)

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

4 open source packages ship an affected version, including org.keycloak:keycloak-model-infinispan and org.keycloak:keycloak-model-jpa. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-model-infinispan` | Maven | All versions | 7.0.1 |
| `org.keycloak:keycloak-model-infinispan` | Maven | All versions | 7.0.1 |
| `org.keycloak:keycloak-model-jpa` | Maven | All versions | 7.0.1 |
| `org.keycloak:keycloak-model-jpa` | Maven | All versions | 7.0.1 |

Products: Redhat Keycloak.

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

Upgrade org.keycloak:keycloak-model-infinispan to 7.0.1 or later.

## Is CVE-2019-14832 being exploited?

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

What it is: CVE-2019-14832 is a medium-severity missing authorization vulnerability in Redhat Keycloak, published on 15 Oct 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-14832 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-model-infinispan (Maven): affected all versions; fixed in 7.0.1
- org.keycloak:keycloak-model-infinispan (Maven): affected all versions; fixed in 7.0.1
- org.keycloak:keycloak-model-jpa (Maven): affected all versions; fixed in 7.0.1
- org.keycloak:keycloak-model-jpa (Maven): affected all versions; fixed in 7.0.1

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

## Sources

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

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