# CVE-2020-14359: Keycloak Gatekeeper vulnerable to bypass on using lower case HTTP headers

> Attackers can bypass Keycloak Gatekeeper authentication by using lowercase HTTP headers when deployed in front of servers like Jetty.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Feb 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-jh6m-3pqw-242h

## What is CVE-2020-14359?

CVE-2020-14359 is a high-severity authentication bypass vulnerability in keycloak, published on 23 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in all versions of Keycloak Gatekeeper, where on using lower case HTTP headers (via cURL) an attacker can bypass our Gatekeeper. Lower case headers are also accepted by some webservers (e.g. Jetty). This means there is no protection when we put a Gatekeeper in front of a Jetty server and use lowercase headers.

Weakness: CWE-305 (Authentication Bypass by Primary Weakness)

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

2 open source packages ship an affected version, including github.com/keycloak/keycloak-gatekeeper. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/keycloak/keycloak-gatekeeper` | Go | All versions to 1.2.8 | None |
| `github.com/keycloak/keycloak-gatekeeper` | Go | All versions to 1.2.8 | None |

Products: Redhat Louketo Proxy.

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

No fix has been published for CVE-2020-14359 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-14359 being exploited?

There is no known exploitation of CVE-2020-14359 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-14359 and fix it if it is affected.

What it is: CVE-2020-14359 is a high-severity authentication bypass vulnerability in keycloak, published on 23 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-14359 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/keycloak/keycloak-gatekeeper (Go): affected all versions up to 1.2.8; no fix listed
- github.com/keycloak/keycloak-gatekeeper (Go): affected all versions up to 1.2.8; 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-2020-14359/ (Markdown: https://insights.sbomify.com/CVE-2020-14359/index.md)
```

## Sources

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

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