{"answers":{"affected":"2 open source packages ship an affected version, including github.com/zitadel/zitadel. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-44399 in the wild and no public exploit code.","fix":"Upgrade github.com/zitadel/zitadel to 2.37.3 or later.","what":"CVE-2023-44399 is a medium-severity vulnerability in zitadel, published on 10 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-44399 and fix it if it is affected.\n\nWhat it is: CVE-2023-44399 is a medium-severity vulnerability in zitadel, published on 10 Oct 2023. 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-2023-44399 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/zitadel/zitadel (Go): affected all versions; fixed in 2.37.3\n- github.com/zitadel/zitadel (Go): affected all versions; fixed in 2.37.3\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-2023-44399/ (Markdown: https://insights.sbomify.com/CVE-2023-44399/index.md)","id":"CVE-2023-44399","markdown":"https://insights.sbomify.com/CVE-2023-44399/index.md","name":"CVE-2023-44399","record":{"aliases":["GHSA-v683-rcxx-vpff"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Identity infrastructure","requires_auth":"none","summary":"Attackers can enumerate valid usernames via password reset flow, bypassing the 'Ignoring unknown usernames' security setting.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"zitadel","vendor":"zitadel"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-640","name":"Weak Password Recovery Mechanism for Forgotten Password"}],"description":"ZITADEL provides identity infrastructure. In versions 2.37.2 and prior, ZITADEL administrators can enable a setting called \"Ignoring unknown usernames\" which helps mitigate attacks that try to guess/enumerate usernames. While this settings was properly working during the authentication process it did not work correctly on the password reset flow. This meant that even if this feature was active that an attacker could use the password reset function to verify if an account exist within ZITADEL. This bug has been patched in versions 2.37.3 and 2.38.0. No known workarounds are available.","ecosystems":["Go"],"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":"ZITADEL's password reset does not respect the \"Ignoring unknown usernames\" setting","id":"CVE-2023-44399","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":2,"n_references":3,"next":{"headline":"Uptime Kuma has Persistentent User Sessions","id":"CVE-2023-44400"},"packages":[{"ecosystem":"Go","fixed":["2.37.3"],"introduced":["0"],"last_affected":[],"package":"github.com/zitadel/zitadel","purl":null,"source":"GHSA-v683-rcxx-vpff"},{"ecosystem":"Go","fixed":["2.37.3"],"introduced":["0"],"last_affected":[],"package":"github.com/zitadel/zitadel","purl":"pkg:golang/github.com/zitadel/zitadel","source":"GHSA-v683-rcxx-vpff"}],"prev":{"headline":"Out-of-bounds write in exiv2","id":"CVE-2023-44398"},"products":["zitadel"],"published":"2023-10-10","related":[{"cvss_score":9.3,"headline":"ZITADEL: 1-Click Account Takeover via XSS in /saml-post Endpoint","id":"CVE-2026-29191","kev_date_added":null,"published":"2026-03-07"},{"cvss_score":9.3,"headline":"ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login","id":"CVE-2025-67494","kev_date_added":null,"published":"2025-12-09"},{"cvss_score":9,"headline":"IDOR Vulnerabilities in ZITADEL's Admin API that Primarily Impact LDAP Configurations","id":"CVE-2025-27507","kev_date_added":null,"published":"2025-03-04"},{"cvss_score":8.7,"headline":"Zitadel Bypass Second Authentication Factor","id":"CVE-2025-64103","kev_date_added":null,"published":"2025-10-29"},{"cvss_score":8.7,"headline":"Zitadel Expired JWT Keys Usable for Authorization Grants","id":"CVE-2025-31123","kev_date_added":null,"published":"2025-03-31"},{"cvss_score":8.7,"headline":"ZITADEL Improper Content-Type Validation Leads to Account Takeover via Stored XSS + CSP Bypass","id":"CVE-2024-29891","kev_date_added":null,"published":"2024-03-27"},{"cvss_score":8.7,"headline":"XSS with User Avatar image in ZITADEL","id":"CVE-2023-46238","kev_date_added":null,"published":"2023-10-26"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-19","vendors":["zitadel"]},"summary":"Attackers can enumerate valid usernames via password reset flow, bypassing the 'Ignoring unknown usernames' security setting.","url":"https://insights.sbomify.com/CVE-2023-44399/"}