# CVE-2017-12160: Keycloak Oauth Implementation Error

> An attacker with a compromised resource can retain indefinite access tokens despite permission revocation, bypassing authorization controls in Keycloak.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Oct 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qc72-gfvw-76h7

## What is CVE-2017-12160?

CVE-2017-12160 is a high-severity authentication bypass vulnerability in Redhat Keycloak, published on 26 Oct 2017. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

It was found that Keycloak oauth would permit an authenticated resource to obtain an access/refresh token pair from the authentication server, permitting indefinite usage in the case of permission revocation. An attacker on an already compromised resource could use this flaw to grant himself continued permissions and possibly conduct further attacks.

Weakness: CWE-287 (Improper Authentication), CWE-285 (Improper Authorization)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-parent` | Maven | All versions | 3.3.0.Final |
| `org.keycloak:keycloak-parent` | Maven | All versions | 3.3.0.Final |

Products: Redhat Keycloak.

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

Upgrade org.keycloak:keycloak-parent to 3.3.0.Final or later.

## Is CVE-2017-12160 being exploited?

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

What it is: CVE-2017-12160 is a high-severity authentication bypass vulnerability in Redhat Keycloak, published on 26 Oct 2017. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-12160 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-parent (Maven): affected all versions; fixed in 3.3.0.Final
- org.keycloak:keycloak-parent (Maven): affected all versions; fixed in 3.3.0.Final

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

## Sources

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

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