{"answers":{"affected":"2 open source packages ship an affected version, including github.com/keycloak/keycloak-gatekeeper. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-14359 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-14359 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2020-14359 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2020-14359 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/keycloak/keycloak-gatekeeper (Go): affected all versions up to 1.2.8; no fix listed\n- github.com/keycloak/keycloak-gatekeeper (Go): affected all versions up to 1.2.8; no fix listed\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2020-14359/ (Markdown: https://insights.sbomify.com/CVE-2020-14359/index.md)","id":"CVE-2020-14359","markdown":"https://insights.sbomify.com/CVE-2020-14359/index.md","name":"CVE-2020-14359","record":{"aliases":["GHSA-jh6m-3pqw-242h"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Keycloak Gatekeeper","requires_auth":"none","summary":"Attackers can bypass Keycloak Gatekeeper authentication by using lowercase HTTP headers when deployed in front of servers like Jetty.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"louketo_proxy","vendor":"redhat"}],"cvss":{"score":7.3,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-305","name":"Authentication Bypass by Primary Weakness"}],"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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Keycloak Gatekeeper vulnerable to bypass on using lower case HTTP headers","id":"CVE-2020-14359","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"auth_bypass","year":"2020"},"n_packages":2,"n_references":2,"next":{"headline":"Memory corruption in xorg-x11-server","id":"CVE-2020-14360"},"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":["1.2.8"],"package":"github.com/keycloak/keycloak-gatekeeper","purl":null,"source":"GHSA-jh6m-3pqw-242h"},{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":["1.2.8"],"package":"github.com/keycloak/keycloak-gatekeeper","purl":"pkg:golang/github.com/keycloak/keycloak-gatekeeper","source":"GHSA-jh6m-3pqw-242h"}],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2020-14358"},"products":["keycloak"],"published":"2021-02-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can bypass Keycloak Gatekeeper authentication by using lowercase HTTP headers when deployed in front of servers like Jetty.","url":"https://insights.sbomify.com/CVE-2020-14359/"}