{"answers":{"affected":"1 open source package ship an affected version, including authentik. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-38371 in the wild and no public exploit code.","fix":"Upgrade authentik to 2024.6.0 or later.","what":"CVE-2024-38371 is a high-severity missing authorization vulnerability in goauthentik authentik, published on 28 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-38371 and fix it if it is affected.\n\nWhat it is: CVE-2024-38371 is a high-severity missing authorization vulnerability in goauthentik authentik, published on 28 Jun 2024. 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-2024-38371 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- authentik (Bitnami): affected all versions; fixed in 2024.6.0\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-2024-38371/ (Markdown: https://insights.sbomify.com/CVE-2024-38371/index.md)","id":"CVE-2024-38371","markdown":"https://insights.sbomify.com/CVE-2024-38371/index.md","name":"CVE-2024-38371","record":{"aliases":["BIT-authentik-2024-38371","GHSA-jq3m-37m7-gp45"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Identity Provider","requires_auth":"none","summary":"Attackers can bypass access controls in the OAuth2 Device Code flow to obtain tokens and access unauthorized applications in authentik.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"authentik","vendor":"goauthentik"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"},{"id":"CWE-284","name":"Improper Access Control"}],"description":"authentik is an open-source Identity Provider. Access restrictions assigned to an application were not checked when using the OAuth2 Device code flow. This could potentially allow users without the correct authorization to get OAuth tokens for an application and access it. This issue has been patched in version(s) 2024.6.0, 2024.2.4 and 2024.4.3.","ecosystems":["Bitnami"],"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":"Insufficient access control for OAuth2 Device Code flow in authentik","id":"CVE-2024-38371","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"missing_authorization","year":"2024"},"n_packages":1,"n_references":4,"next":{"headline":"Undici vulnerable to data leak when using response.arrayBuffer()","id":"CVE-2024-38372"},"packages":[{"ecosystem":"Bitnami","fixed":["2024.6.0"],"introduced":["0"],"last_affected":[],"package":"authentik","purl":"pkg:bitnami/authentik","source":"BIT-authentik-2024-38371"}],"prev":{"headline":"GLPI allows API document download without rights","id":"CVE-2024-38370"},"products":["authentik"],"published":"2024-06-28","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":"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-08-02","vendors":["goauthentik"]},"summary":"Attackers can bypass access controls in the OAuth2 Device Code flow to obtain tokens and access unauthorized applications in authentik.","url":"https://insights.sbomify.com/CVE-2024-38371/"}