{"answers":{"affected":"2 open source packages ship an affected version, including org.keycloak:keycloak-services. It affects 2 products.","exploited":"There is no known exploitation of CVE-2021-3754 in the wild and no public exploit code.","fix":"Upgrade org.keycloak:keycloak-services to 24.0.1 or later.","what":"CVE-2021-3754 is a medium-severity vulnerability in Redhat Keycloak, published on 26 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-3754 and fix it if it is affected.\n\nWhat it is: CVE-2021-3754 is a medium-severity vulnerability in Redhat Keycloak, published on 26 Aug 2022. 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-2021-3754 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 24.0.1\n- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 24.0.1\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-3754/ (Markdown: https://insights.sbomify.com/CVE-2021-3754/index.md)","id":"CVE-2021-3754","markdown":"https://insights.sbomify.com/CVE-2021-3754/index.md","name":"CVE-2021-3754","record":{"aliases":["GHSA-4vc8-pg5c-vg4x"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Keycloak identity server","requires_auth":"none","summary":"Attackers can register with usernames matching existing user emails, potentially disrupting password recovery processes for legitimate users.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"keycloak","vendor":"redhat"},{"product":"single_sign-on","vendor":"redhat"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"A flaw was found in keycloak where an attacker is able to register himself with the username same as the email ID of any existing user. This may cause trouble in getting password recovery email in case the user forgets the password.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":"2023-09-07","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2023-09-07T07:49:21Z","kind":"github_poc","ref":"https://github.com/7Ragnarok7/CVE-2021-3754","stars":1,"title":"Vulnerability details and exploit for CVE-2021-3754"}],"tier":"poc_unverified"},"has_fix":true,"headline":"Keycloak's improper input validation allows using email as username","id":"CVE-2021-3754","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"redhat:keycloak","products":["redhat:keycloak","redhat:single_sign-on"],"type":"business_logic","year":"2021"},"n_packages":2,"n_references":2,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2021-3755"},"packages":[{"ecosystem":"Maven","fixed":["24.0.1"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-services","purl":null,"source":"GHSA-4vc8-pg5c-vg4x"},{"ecosystem":"Maven","fixed":["24.0.1"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-services","purl":"pkg:maven/org.keycloak/keycloak-services","source":"GHSA-4vc8-pg5c-vg4x"}],"prev":{"headline":"Race condition in kernel","id":"CVE-2021-3753"},"products":["keycloak"],"published":"2022-08-26","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can register with usernames matching existing user emails, potentially disrupting password recovery processes for legitimate users.","url":"https://insights.sbomify.com/CVE-2021-3754/"}