Skip to content
Fencer Vulns
high 7.3

CVE-2020-14359 json

Keycloak Gatekeeper vulnerable to bypass on using lower case HTTP headers

published 2021-02-23 5 y ago modified 2026-06-17 4 mo ago also GHSA-jh6m-3pqw-242h , EUVD-2022-1075

cvss
7.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 60%
public exploits
0
none known

Summary

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.

Patch / fix

  • keycloak Arch Linux 16.0.0-1

arch linux advisories AVG-1332

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-14359 updated cvss 7.3

keycloak-gatekeeper: gatekeeper bypass via cURL when using lower case HTTP headers

  • Red Hat Single Sign-On 7 keycloak-gatekeeper keycloak-gatekeeper
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.93% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 7.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.1 7.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Affected packages

ecosystem package affected fixed in
go github.com/keycloak/keycloak-gatekeeper
<=1.2.8
 no fix listed

Affected products

  • n/a keycloak

Classification

Weakness
  • CWE-305 Authentication Bypass by Primary Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.