{"answers":{"affected":"2 open source packages ship an affected version, including org.keycloak:keycloak-core. It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-14837 in the wild and no public exploit code.","fix":"Upgrade org.keycloak:keycloak-core to 8.0.0 or later.","what":"CVE-2019-14837 is a critical vulnerability in Redhat Keycloak, published on 7 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-14837 and fix it if it is affected.\n\nWhat it is: CVE-2019-14837 is a critical vulnerability in Redhat Keycloak, published on 7 Jan 2020. 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-2019-14837 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 8.0.0\n- org.keycloak:keycloak-core (Maven): affected all versions; fixed in 8.0.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-2019-14837/ (Markdown: https://insights.sbomify.com/CVE-2019-14837/index.md)","id":"CVE-2019-14837","markdown":"https://insights.sbomify.com/CVE-2019-14837/index.md","name":"CVE-2019-14837","record":{"aliases":["GHSA-cf8f-w2c5-p5jr"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Keycloak identity server","requires_auth":"none","summary":"An attacker controlling a specific domain can reset passwords for Keycloak service accounts by exploiting hardcoded email generation logic, leading to account takeover.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"keycloak","vendor":"redhat"},{"product":"single_sign-on","vendor":"redhat"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"},{"id":"CWE-547","name":"Use of Hard-coded, Security-relevant Constants"}],"description":"A flaw was found in keycloack before version 8.0.0. The owner of 'placeholder.org' domain can setup mail server on this domain and knowing only name of a client can reset password and then log in. For example, for client name 'test' the email address will be 'service-account-test@placeholder.org'.","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":"keycloak vulnerable to unauthorized login via mail server setup","id":"CVE-2019-14837","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"redhat:keycloak","products":["redhat:keycloak","redhat:single_sign-on"],"type":"hardcoded_credentials","year":"2019"},"n_packages":2,"n_references":3,"next":{"headline":"Wildfly Authorization Misconfiguration","id":"CVE-2019-14838"},"packages":[{"ecosystem":"Maven","fixed":["8.0.0"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-core","purl":null,"source":"GHSA-cf8f-w2c5-p5jr"},{"ecosystem":"Maven","fixed":["8.0.0"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-core","purl":"pkg:maven/org.keycloak/keycloak-core","source":"GHSA-cf8f-w2c5-p5jr"}],"prev":{"headline":"Cross-site request forgery in Red Hat 3scale API Management","id":"CVE-2019-14836"},"products":["keycloak"],"published":"2020-01-07","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"}],"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":["Red Hat"]},"summary":"An attacker controlling a specific domain can reset passwords for Keycloak service accounts by exploiting hardcoded email generation logic, leading to account takeover.","url":"https://insights.sbomify.com/CVE-2019-14837/"}