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.
Metrics
Affected Vendors & Products
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-0260 | 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. |
Github GHSA |
GHSA-5g66-628f-7cvj | Omniauth::MicrosoftGraph Account takeover (nOAuth) |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Tue, 17 Jun 2025 21:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2025-06-17T20:29:07.166Z
Reserved: 2023-12-29T03:00:44.954Z
Link: CVE-2024-21632
Updated: 2024-08-01T22:27:35.736Z
Status : Modified
Published: 2024-01-02T22:15:10.103
Modified: 2024-11-21T08:54:46.027
Link: CVE-2024-21632
No data.
OpenCVE Enrichment
No data.
Weaknesses
EUVD
Github GHSA