{"answers":{"affected":"2 open source packages ship an affected version, including org.keycloak:keycloak-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-14637 in the wild and no public exploit code.","fix":"Upgrade org.keycloak:keycloak-core to 4.6.0 or later.","what":"CVE-2018-14637 is a medium-severity authentication bypass vulnerability in Redhat Keycloak, published on 30 Nov 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-14637 and fix it if it is affected.\n\nWhat it is: CVE-2018-14637 is a medium-severity authentication bypass vulnerability in Redhat Keycloak, published on 30 Nov 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-14637 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.keycloak:keycloak-core (Maven): affected all versions; fixed in 4.6.0\n- org.keycloak:keycloak-core (Maven): affected all versions; fixed in 4.6.0\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-2018-14637/ (Markdown: https://insights.sbomify.com/CVE-2018-14637/index.md)","id":"CVE-2018-14637","markdown":"https://insights.sbomify.com/CVE-2018-14637/index.md","name":"CVE-2018-14637","record":{"aliases":["GHSA-gf2j-7qwg-4f5x"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Identity and Access Management","requires_auth":"none","summary":"Attackers can bypass authentication by replaying expired SAML assertions in Keycloak, allowing unauthorized access to protected resources.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"keycloak","vendor":"redhat"}],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"},{"id":"CWE-285","name":"Improper Authorization"}],"description":"The SAML broker consumer endpoint in Keycloak before version 4.6.0.Final ignores expiration conditions on SAML assertions. An attacker can exploit this vulnerability to perform a replay attack.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Improper Authentication in Keycloak","id":"CVE-2018-14637","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"redhat:keycloak","products":["redhat:keycloak"],"type":"auth_bypass","year":"2018"},"n_packages":2,"n_references":1,"next":{"headline":"Denial of service in 389-ds-base","id":"CVE-2018-14638"},"packages":[{"ecosystem":"Maven","fixed":["4.6.0"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-core","purl":null,"source":"GHSA-gf2j-7qwg-4f5x"},{"ecosystem":"Maven","fixed":["4.6.0"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-core","purl":"pkg:maven/org.keycloak/keycloak-core","source":"GHSA-gf2j-7qwg-4f5x"}],"prev":{"headline":"Openstack Neutron vulnerable to eavesdropping on private traffic","id":"CVE-2018-14636"},"products":["keycloak"],"published":"2018-11-30","related":[{"cvss_score":10,"headline":"Keycloak vulnerable to cross-site scripting when validating URI-schemes on SAML and OIDC","id":"CVE-2022-4361","kev_date_added":null,"published":"2023-07-07"},{"cvss_score":9.8,"headline":"Keycloak vulnerable to privilege escalation on Token Exchange feature","id":"CVE-2022-1245","kev_date_added":null,"published":"2022-07-07"},{"cvss_score":9.6,"headline":"keycloak Self Stored Cross-site Scripting vulnerability","id":"CVE-2021-20195","kev_date_added":null,"published":"2021-05-28"},{"cvss_score":9.3,"headline":"Keycloak Authentication Error","id":"CVE-2019-14910","kev_date_added":null,"published":"2019-12-05"},{"cvss_score":9.3,"headline":"Keycloak Authentication Error","id":"CVE-2019-14909","kev_date_added":null,"published":"2019-12-04"},{"cvss_score":9.1,"headline":"Keycloak vulnerable to path traversal via double URL encoding","id":"CVE-2022-3782","kev_date_added":null,"published":"2023-01-11"},{"cvss_score":9.1,"headline":"keycloak vulnerable to unauthorized login via mail server setup","id":"CVE-2019-14837","kev_date_added":null,"published":"2020-01-07"}],"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-05","vendors":["[UNKNOWN]"]},"summary":"Attackers can bypass authentication by replaying expired SAML assertions in Keycloak, allowing unauthorized access to protected resources.","url":"https://insights.sbomify.com/CVE-2018-14637/"}