Vulnerability 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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Recognizeapp | Omniauth\ | < 2.0.0, \ |
Related Weaknesses (CWE)
References
- https://github.com/synth/omniauth-microsoft_graph/commit/f132078389612b797c872b4Patch
- https://github.com/synth/omniauth-microsoft_graph/security/advisories/GHSA-5g66-Vendor Advisory
- https://www.descope.com/blog/post/noauthExploit
- https://github.com/synth/omniauth-microsoft_graph/commit/f132078389612b797c872b4Patch
- https://github.com/synth/omniauth-microsoft_graph/security/advisories/GHSA-5g66-Vendor Advisory
- https://www.descope.com/blog/post/noauthExploit
FAQ
What is CVE-2024-21632?
CVE-2024-21632 is a vulnerability with a CVSS score of 8.6 (HIGH). 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...
How severe is CVE-2024-21632?
CVE-2024-21632 has been rated HIGH with a CVSS base score of 8.6/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2024-21632?
Check the references section above for vendor advisories and patch information. Affected products include: Recognizeapp Omniauth\.