{"answers":{"affected":"5 open source packages ship an affected version, including @goauthentik/api and authentik. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-39522 in the wild and no public exploit code.","fix":"Upgrade @goauthentik/api to a fixed version for your release line: 2023.5.6 or 2023.6.2.","what":"CVE-2023-39522 is a medium-severity vulnerability in goauthentik authentik, published on 29 Aug 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-39522 and fix it if it is affected.\n\nWhat it is: CVE-2023-39522 is a medium-severity vulnerability in goauthentik authentik, published on 29 Aug 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-39522 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @goauthentik/api (npm): affected all versions; fixed in 2023.5.6\n- @goauthentik/api (npm): affected all versions; fixed in 2023.5.6\n- @goauthentik/api (npm): affected from 2023.6.0; fixed in 2023.6.2\n- @goauthentik/api (npm): affected from 2023.6.0; fixed in 2023.6.2\n- authentik (Bitnami): affected all versions; fixed in 2023.5.6, 2023.6.2\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-39522/ (Markdown: https://insights.sbomify.com/CVE-2023-39522/index.md)","id":"CVE-2023-39522","markdown":"https://insights.sbomify.com/CVE-2023-39522/index.md","name":"CVE-2023-39522","record":{"aliases":["BIT-authentik-2023-39522","GHSA-vmf9-6pcv-xr87"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Identity Provider","requires_auth":"none","summary":"Attackers can enumerate valid usernames via the recovery flow, revealing user existence in goauthentik Identity Provider deployments.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"authentik","vendor":"goauthentik"}],"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-203","name":"Observable Discrepancy"}],"description":"goauthentik is an open-source Identity Provider. In affected versions using a recovery flow with an identification stage an attacker is able to determine if a username exists. Only setups configured with a recovery flow are impacted by this. Anyone with a user account on a system with the recovery flow described above is susceptible to having their username/email revealed as existing. An attacker can easily enumerate and check users' existence using the recovery flow, as a clear message is shown when a user doesn't exist. Depending on configuration this can either be done by username, email, or both. This issue has been addressed in versions 2023.5.6 and 2023.6.2. Users are advised to upgrade. There are no known workarounds for this issue.","ecosystems":["Bitnami","npm"],"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":"Username enumeration attack in goauthentik","id":"CVE-2023-39522","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":5,"n_references":2,"next":{"headline":"ScanCode.io command injection in docker image fetch process","id":"CVE-2023-39523"},"packages":[{"ecosystem":"Bitnami","fixed":["2023.5.6","2023.6.2"],"introduced":["0","2023.6.0"],"last_affected":[],"package":"authentik","purl":"pkg:bitnami/authentik","source":"BIT-authentik-2023-39522"},{"ecosystem":"npm","fixed":["2023.5.6"],"introduced":["0"],"last_affected":[],"package":"@goauthentik/api","purl":null,"source":"GHSA-vmf9-6pcv-xr87"},{"ecosystem":"npm","fixed":["2023.5.6"],"introduced":["0"],"last_affected":[],"package":"@goauthentik/api","purl":"pkg:npm/%40goauthentik/api","source":"GHSA-vmf9-6pcv-xr87"},{"ecosystem":"npm","fixed":["2023.6.2"],"introduced":["2023.6.0"],"last_affected":[],"package":"@goauthentik/api","purl":null,"source":"GHSA-vmf9-6pcv-xr87"},{"ecosystem":"npm","fixed":["2023.6.2"],"introduced":["2023.6.0"],"last_affected":[],"package":"@goauthentik/api","purl":"pkg:npm/%40goauthentik/api","source":"GHSA-vmf9-6pcv-xr87"}],"prev":{"headline":"Tuleap vulnerable to Cross-site Scripting on the success message of a kanban deletion","id":"CVE-2023-39521"},"products":["authentik"],"published":"2023-08-29","related":[{"cvss_score":9.8,"headline":"authentik: SourceStage bypass via empty POST","id":"CVE-2026-49448","kev_date_added":null,"published":"2026-06-02"},{"cvss_score":9.7,"headline":"authentik potential installation takeover when default admin user is deleted","id":"CVE-2023-46249","kev_date_added":null,"published":"2023-10-31"},{"cvss_score":9.4,"headline":"authentik vulnerable to Improper Authentication via invitation URL token reuse","id":"CVE-2022-23555","kev_date_added":null,"published":"2022-12-28"},{"cvss_score":9.3,"headline":"authentik: Reflected XSS in SFE AutosubmitStage allows IDP account takeover","id":"CVE-2026-42849","kev_date_added":null,"published":"2026-06-02"},{"cvss_score":9.1,"headline":"authentik affected by Remote Code Execution via Context Key Injection in PropertyMapping Test Endpoint","id":"CVE-2026-25227","kev_date_added":null,"published":"2026-02-12"},{"cvss_score":9.1,"headline":"authentik vulnerable to password authentication bypass via X-Forwarded-For HTTP header","id":"CVE-2024-47070","kev_date_added":null,"published":"2024-09-27"},{"cvss_score":9.1,"headline":"Insufficient user check in FlowTokens by Email stage","id":"CVE-2023-26481","kev_date_added":null,"published":"2023-03-04"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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-10-01","vendors":["goauthentik"]},"summary":"Attackers can enumerate valid usernames via the recovery flow, revealing user existence in goauthentik Identity Provider deployments.","url":"https://insights.sbomify.com/CVE-2023-39522/"}