CVE-2024-21632: Omniauth::MicrosoftGraph Account takeover (nOAuth)
Summary 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
Published Jan 3, 2024 · Updated Jan 9, 2024
Affected packages
omniauth-microsoft_graph
- Ecosystem
- RubyGems
- Affected
- < 2.0.0
- Fixed in
- 2.0.0
- Check
bundle info omniauth-microsoft_graph
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
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
Credited to makuga01.
References
- https://github.com/synth/omniauth-microsoft_graph/security/advisories/GHSA-5g66-628f-7cvj
- https://nvd.nist.gov/vuln/detail/CVE-2024-21632
- https://github.com/synth/omniauth-microsoft_graph/commit/5ffd62690ca0e46978f2fc7d83b18d28edde7795
- https://github.com/synth/omniauth-microsoft_graph/commit/f132078389612b797c872b45bd0e0b47382414c1
- https://www.descope.com/blog/post/noauth
- https://github.com/advisories/GHSA-5g66-628f-7cvj
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
