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.
References
Configurations
History
09 Jan 2024, 17:45
Type | Values Removed | Values Added |
---|---|---|
CPE | cpe:2.3:a:recognizeapp:omniauth\:\:microsoftgraph:*:*:*:*:*:ruby:*:* | |
References | () https://github.com/synth/omniauth-microsoft_graph/security/advisories/GHSA-5g66-628f-7cvj - Vendor Advisory | |
References | () https://www.descope.com/blog/post/noauth - Exploit | |
References | () https://github.com/synth/omniauth-microsoft_graph/commit/f132078389612b797c872b45bd0e0b47382414c1 - Patch | |
CVSS |
v2 : v3 : |
v2 : unknown
v3 : 9.8 |
First Time |
Recognizeapp
Recognizeapp omniauth\ |
02 Jan 2024, 22:15
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2024-01-02 22:15
Updated : 2024-02-28 20:54
NVD link : CVE-2024-21632
Mitre link : CVE-2024-21632
CVE.ORG link : CVE-2024-21632
JSON object : View
Products Affected
recognizeapp
- omniauth\
CWE
CWE-287
Improper Authentication