High severity8.6NVD Advisory· Published Jan 2, 2024· Updated Jun 17, 2026
CVE-2024-21632
CVE-2024-21632
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
omniauth-microsoft_graphRubyGems | < 2.0.0 | 2.0.0 |
Affected products
3- cpe:2.3:a:recognizeapp:omniauth\:\:microsoftgraph:*:*:*:*:*:ruby:*:*Range: <2.0.0
- Range: < 2.0.0
Patches
Vulnerability mechanics
References
6- github.com/synth/omniauth-microsoft_graph/commit/f132078389612b797c872b45bd0e0b47382414c1nvdPatchWEB
- www.descope.com/blog/post/noauthnvdExploitWEB
- github.com/advisories/GHSA-5g66-628f-7cvjghsaADVISORY
- github.com/synth/omniauth-microsoft_graph/security/advisories/GHSA-5g66-628f-7cvjnvdVendor AdvisoryWEB
- nvd.nist.gov/vuln/detail/CVE-2024-21632ghsaADVISORY
- github.com/synth/omniauth-microsoft_graph/commit/5ffd62690ca0e46978f2fc7d83b18d28edde7795ghsaWEB
News mentions
0No linked articles in our index yet.