{"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-2021-20262 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-20262 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-20262 is a medium-severity authentication bypass vulnerability in Redhat Keycloak, published on 9 Mar 2021. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-20262 and fix it if it is affected.\n\nWhat it is: CVE-2021-20262 is a medium-severity authentication bypass vulnerability in Redhat Keycloak, published on 9 Mar 2021. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-20262 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.keycloak:keycloak-core (Maven): affected all versions up to 12.0.4; no fix listed\n- org.keycloak:keycloak-core (Maven): affected all versions up to 12.0.4; 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-2021-20262/ (Markdown: https://insights.sbomify.com/CVE-2021-20262/index.md)","id":"CVE-2021-20262","markdown":"https://insights.sbomify.com/CVE-2021-20262/index.md","name":"CVE-2021-20262","record":{"aliases":["GHSA-xf46-8vvp-4hxx"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Keycloak identity server","requires_auth":"none","summary":"Attackers with temporary physical access can take over accounts because Keycloak fails to require re-authentication during password updates.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"keycloak","vendor":"redhat"},{"product":"single_sign-on","vendor":"redhat"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"A flaw was found in Keycloak 12.0.0 where re-authentication does not occur while updating the password. This flaw allows an attacker to take over an account if they can obtain temporary, physical access to a user’s browser. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.","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":false,"headline":"Keycloak Missing authentication for critical function","id":"CVE-2021-20262","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"redhat:keycloak","products":["redhat:keycloak","redhat:single_sign-on"],"type":"auth_bypass","year":"2021"},"n_packages":2,"n_references":1,"next":{"headline":"Privilege escalation in QEMU","id":"CVE-2021-20263"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["12.0.4"],"package":"org.keycloak:keycloak-core","purl":null,"source":"GHSA-xf46-8vvp-4hxx"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["12.0.4"],"package":"org.keycloak:keycloak-core","purl":"pkg:maven/org.keycloak/keycloak-core","source":"GHSA-xf46-8vvp-4hxx"}],"prev":{"headline":"Race condition in kernel","id":"CVE-2021-20261"},"products":["keycloak"],"published":"2021-03-09","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-03","vendors":["n/a"]},"summary":"Attackers with temporary physical access can take over accounts because Keycloak fails to require re-authentication during password updates.","url":"https://insights.sbomify.com/CVE-2021-20262/"}