omniauth-microsoft_graph vulnerable to account takeover (nOAuth)
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2024-21632
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 00:55 UTC · Revision 1
Source evidence
omniauth-microsoft_graph vulnerable to account takeover (nOAuth)
core-osv · Original sourcePublished 2 Jan 2024, 21:54 UTC
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.
osv:CVE-2024-21632
Complete source record
{
"id": "c2ed6e51602cdbd4f8f522e55296d77cce42eacb77e19c719931cabd1b53340e",
"url": "https://osv.dev/vulnerability/CVE-2024-21632",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "omniauth-microsoft_graph vulnerable to account takeover (nOAuth)",
"summary": "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.",
"evidence": "osv:CVE-2024-21632",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2024-21632",
"aliases": [
"CVE-2024-21632",
"GHSA-5g66-628f-7cvj"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/synth/omniauth-microsoft_graph",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "cba8a27264d230fffa011ab9df461eb918fef375"
},
{
"fixed": "f132078389612b797c872b45bd0e0b47382414c1"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:recognizeapp:omniauth\\:\\:microsoftgraph:*:*:*:*:*:ruby:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "2.0.0"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "f132078389612b797c872b45bd0e0b47382414c1"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"1.1.0",
"1.0.0",
"0.3.3",
"0.3.2",
"0.3.1",
"0.3.0",
"pre-oauth-v2"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-21632.json"
}
}
],
"modified": "2026-10-28T02:30:24.739638890Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/21xxx/CVE-2024-21632.json",
"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/f132078389612b797c872b45bd0e0b47382414c1",
"https://www.descope.com/blog/post/noauth"
],
"provider_metadata": {
"cwe_ids": [
"CWE-287"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/21xxx/CVE-2024-21632.json"
}
},
"related_cves": [
{
"value": "CVE-2024-21632",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 491362,
"published_at": "2024-01-02T21:54:54.527+00:00"
}