{"answers":{"affected":"2 open source packages ship an affected version, including omniauth-microsoft_graph. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-21632 in the wild and no public exploit code.","fix":"Upgrade omniauth-microsoft_graph to 2.0.0 or later.","what":"CVE-2024-21632 is a high-severity authentication bypass vulnerability in synth omniauth-microsoft_graph, published on 2 Jan 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-21632 and fix it if it is affected.\n\nWhat it is: CVE-2024-21632 is a high-severity authentication bypass vulnerability in synth omniauth-microsoft_graph, published on 2 Jan 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-21632 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- omniauth-microsoft_graph (RubyGems): affected all versions; fixed in 2.0.0\n- omniauth-microsoft_graph (RubyGems): affected all versions; fixed in 2.0.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-21632/ (Markdown: https://insights.sbomify.com/CVE-2024-21632/index.md)","id":"CVE-2024-21632","markdown":"https://insights.sbomify.com/CVE-2024-21632/index.md","name":"CVE-2024-21632","record":{"aliases":["GHSA-5g66-628f-7cvj"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Ruby authentication library","requires_auth":"none","summary":"Attackers can take over accounts if the email attribute is trusted without validation, requiring a fix in the omniauth-microsoft_graph library.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"omniauth\\","vendor":"recognizeapp"}],"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-287","name":"Improper Authentication"}],"description":"omniauth-microsoft_graph provides an Omniauth strategy for the Microsoft Graph API. Prior to versions 2.0.0, the implementation did not validate the legitimacy of the `email` attribute of the user nor did it give/document an option to do so, making it susceptible to nOAuth misconfiguration in cases when the `email` is used as a trusted user identifier. This could lead to account takeover. Version 2.0.0 contains a fix for this issue.","ecosystems":["RubyGems"],"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":"omniauth-microsoft_graph vulnerable to account takeover (nOAuth)","id":"CVE-2024-21632","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"auth_bypass","year":"2024"},"n_packages":2,"n_references":3,"next":{"headline":"Arbitrary file write on Decoding","id":"CVE-2024-21633"},"packages":[{"ecosystem":"RubyGems","fixed":["2.0.0"],"introduced":["0"],"last_affected":[],"package":"omniauth-microsoft_graph","purl":null,"source":"GHSA-5g66-628f-7cvj"},{"ecosystem":"RubyGems","fixed":["2.0.0"],"introduced":["0"],"last_affected":[],"package":"omniauth-microsoft_graph","purl":"pkg:gem/omniauth-microsoft_graph","source":"GHSA-5g66-628f-7cvj"}],"prev":{"headline":"Integer overflow in URI leading to potential host spoofing","id":"CVE-2024-21631"},"products":["omniauth-microsoft_graph"],"published":"2024-01-02","related":[],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-06-17","vendors":["synth"]},"summary":"Attackers can take over accounts if the email attribute is trusted without validation, requiring a fix in the omniauth-microsoft_graph library.","url":"https://insights.sbomify.com/CVE-2024-21632/"}