{"answers":{"affected":"2 open source packages ship an affected version, including org.keycloak:keycloak-parent. It affects 2 products.","exploited":"There is no known exploitation of CVE-2018-14657 in the wild and no public exploit code.","fix":"Upgrade org.keycloak:keycloak-parent to 4.6.0.Final or later.","what":"CVE-2018-14657 is a medium-severity vulnerability in Redhat Keycloak, published on 13 Nov 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-14657 and fix it if it is affected.\n\nWhat it is: CVE-2018-14657 is a medium-severity vulnerability in Redhat Keycloak, published on 13 Nov 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-14657 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.keycloak:keycloak-parent (Maven): affected all versions; fixed in 4.6.0.Final\n- org.keycloak:keycloak-parent (Maven): affected all versions; fixed in 4.6.0.Final\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-14657/ (Markdown: https://insights.sbomify.com/CVE-2018-14657/index.md)","id":"CVE-2018-14657","markdown":"https://insights.sbomify.com/CVE-2018-14657/index.md","name":"CVE-2018-14657","record":{"aliases":["GHSA-85v8-vx4w-q684"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Keycloak identity server","requires_auth":"low_privilege","summary":"Attackers can bypass brute force protection in Keycloak when TOTP is enabled, allowing unlimited login attempts.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"keycloak","vendor":"redhat"},{"product":"single_sign-on","vendor":"redhat"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"}],"description":"A flaw was found in Keycloak 4.2.1.Final, 4.3.0.Final. When TOPT enabled, an improper implementation of the Brute Force detection algorithm will not enforce its protection measures.","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 Improper Bruteforce Detection","id":"CVE-2018-14657","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"redhat:keycloak","products":["redhat:keycloak","redhat:single_sign-on"],"type":"security_feature_bypass","year":"2018"},"n_packages":2,"n_references":4,"next":{"headline":"Keycloak Open Redirect","id":"CVE-2018-14658"},"packages":[{"ecosystem":"Maven","fixed":["4.6.0.Final"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-parent","purl":null,"source":"GHSA-85v8-vx4w-q684"},{"ecosystem":"Maven","fixed":["4.6.0.Final"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-parent","purl":"pkg:maven/org.keycloak/keycloak-parent","source":"GHSA-85v8-vx4w-q684"}],"prev":{"headline":"Information disclosure in kernel","id":"CVE-2018-14656"},"products":["keycloak"],"published":"2018-11-13","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":["Red Hat"]},"summary":"Attackers can bypass brute force protection in Keycloak when TOTP is enabled, allowing unlimited login attempts.","url":"https://insights.sbomify.com/CVE-2018-14657/"}