{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-46241 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-46241 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-46241 is a critical authentication bypass vulnerability in discourse-microsoft-auth, published on 21 Feb 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-2023-46241 and fix it if it is affected.\n\nWhat it is: CVE-2023-46241 is a critical authentication bypass vulnerability in discourse-microsoft-auth, published on 21 Feb 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-2023-46241 in the wild and no public exploit code.\n\nAffected product: discourse-microsoft-auth. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-46241/ (Markdown: https://insights.sbomify.com/CVE-2023-46241/index.md)","id":"CVE-2023-46241","markdown":"https://insights.sbomify.com/CVE-2023-46241/index.md","name":"CVE-2023-46241","record":{"aliases":["GHSA-2w32-w539-3m7r"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Discourse Microsoft Auth","requires_auth":"none","summary":"Attackers can take over Discourse accounts via unverified emails when Microsoft authentication is configured for multi-tenant environments.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"microsoft_authentication","vendor":"discourse"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"`discourse-microsoft-auth` is a plugin that enables authentication via Microsoft. On sites with the `discourse-microsoft-auth` plugin enabled, an attack can potentially take control of a victim's Discourse account. Sites that have configured their application's account type to any options other than `Accounts in this organizational directory only (O365 only - Single tenant)` are vulnerable. This vulnerability has been patched in commit c40665f44509724b64938c85def9fb2e79f62ec8 of `discourse-microsoft-auth`. A `microsoft_auth:revoke` rake task has also been added which will deactivate and log out all users that have connected their accounts to Microsoft. User API keys as well as API keys created by those users will also be revoked. The rake task will also remove the connection records to Microsoft for those users. This will allow affected users to re-verify their account emails as well as reconnect their Discourse account to Microsoft for authentication. As a workaround, disable the `discourse-microsoft-auth` plugin by setting the `microsoft_auth_enabled` site setting to `false`. Run the `microsoft_auth:log_out_users` rake task to log out all users with associated Microsoft accounts.","ecosystems":[],"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":"Potential account take over due to unverified emails from Microsoft Identity Platform","id":"CVE-2023-46241","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"Code injection in XWiki Platform","id":"CVE-2023-46242"},"packages":[],"prev":{"headline":"CodeIgniter4 vulnerable to information disclosure when detailed error report is displayed in production environment","id":"CVE-2023-46240"},"products":["discourse-microsoft-auth"],"published":"2024-02-21","related":[],"sources":[{"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-27","vendors":["discourse"]},"summary":"Attackers can take over Discourse accounts via unverified emails when Microsoft authentication is configured for multi-tenant environments.","url":"https://insights.sbomify.com/CVE-2023-46241/"}