Omniauth Microsoft Graph
Approved changes feed: RSS · Atom
cpe:2.3:a:synth:omniauth-microsoft_graph:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Synth (f78e8b7b-3cc5-5e8b-a3b2-d88bf6b1b3c1) |
|---|---|
| Product | Omniauth Microsoft Graph (1ebc3acd-7c15-5126-b7fc-ee45353cf2c7) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-21632 |
vulnerable | 2026-06-08 06:27:36.254758 |
omniauth-microsoft_graph vulnerable to account takeover (nOAuth)
HIGH (8.6)
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.
Published: 2024-01-02T21:54:54.527Z
Updated: 2025-06-17T20:29:07.166Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.