{"id":"CVE-2024-21632","aliases":["EUVD-2024-0260","GHSA-5g66-628f-7cvj"],"status":"published","title":"omniauth-microsoft_graph vulnerable to account takeover (nOAuth)","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.","severity":{"version":"3.1","score":8.6,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-10","score":0.00904,"percentile":0.60098,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-287"],"published":"2024-01-02T21:54:54Z","modified":"2026-10-28T02:30:24Z","fixes":[{"ecosystem":"RubyGems","package":"omniauth-microsoft_graph","fixed_in":["2.0.0"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"RubyGems","package":"omniauth-microsoft_graph","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.0"}]}]},{"source":"osv","ecosystem":"RubyGems","package":"omniauth-microsoft_graph","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.0"}]}],"versions":["0.1.0","0.1.1","0.2.0","0.2.1","0.3.0","0.3.1","0.3.2","0.3.3","1.0.0","1.1.0","1.2.0"]}],"products":[{"vendor":"recognizeapp","product":"omniauth\\"},{"vendor":"synth","product":"omniauth-microsoft_graph"}],"references":[{"url":"https://github.com/synth/omniauth-microsoft_graph/security/advisories/GHSA-5g66-628f-7cvj","tags":["x_refsource_CONFIRM","x_transferred","Vendor Advisory","advisory","web"]},{"url":"https://github.com/synth/omniauth-microsoft_graph/commit/f132078389612b797c872b45bd0e0b47382414c1","tags":["x_refsource_MISC","x_transferred","Patch","fix","web"]},{"url":"https://www.descope.com/blog/post/noauth","tags":["x_refsource_MISC","x_transferred","Exploit","article","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-21632","tags":["advisory"]},{"url":"https://github.com/synth/omniauth-microsoft_graph/commit/5ffd62690ca0e46978f2fc7d83b18d28edde7795","tags":["web"]},{"url":"https://github.com/advisories/GHSA-5g66-628f-7cvj"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/21xxx/CVE-2024-21632.json","tags":["advisory"]},{"url":"https://github.com/synth/omniauth-microsoft_graph","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2024-21632","title":"omniauth-microsoft_graph vulnerable to account takeover (nOAuth)","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.\n","status":"published","published":"2024-01-02T21:54:54.527Z","modified":"2025-06-17T20:29:07.166Z","cvss":[{"version":"3.1","score":8.6,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L","level":"high","assessor":"cna"}],"cwes":["CWE-287"],"updated_at":"2026-11-02T14:34:04.681315Z"}],"euvd":[{"id":"EUVD-2024-0260","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.\n","status":"published","published":"2024-01-02T21:54:54Z","modified":"2025-06-17T20:29:07Z","cvss":[{"version":"3.1","score":8.6,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L","level":"high"}],"updated_at":"2026-11-02T20:32:21.932311Z"}],"ghsa":[{"id":"GHSA-5g66-628f-7cvj","title":"Omniauth::MicrosoftGraph Account takeover (nOAuth)","description":"### Summary\nThe 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](https://www.descope.com/blog/post/noauth) misconfiguration in cases when the `email` is used as a trusted user identifier\n","status":"published","published":"2024-01-03T21:46:46Z","modified":"2024-01-09T21:57:03Z","cvss":[{"version":"3.1","score":8.6,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L","level":"high"}],"cwes":["CWE-287"],"updated_at":"2026-11-02T14:37:30.183224Z"}],"nvd":[{"id":"CVE-2024-21632","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.\n","status":"published","published":"2024-01-02T22:15:10.103Z","modified":"2026-06-17T07:09:53.257Z","cvss":[{"version":"3.1","score":8.6,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L","level":"high","assessor":"secondary"},{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical","assessor":"primary"}],"cwes":["CWE-287"],"updated_at":"2026-11-02T14:09:30.070039Z"}],"osv":[{"id":"CVE-2024-21632","title":"omniauth-microsoft_graph vulnerable to account takeover (nOAuth)","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.\n","status":"published","published":"2024-01-02T21:54:54.527Z","modified":"2026-10-28T02:30:24.73963889Z","cvss":[{"version":"3.1","score":8.6,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L","level":"high"}],"cwes":["CWE-287"],"updated_at":"2026-11-02T15:44:38.577405Z"},{"id":"GHSA-5g66-628f-7cvj","title":"Omniauth::MicrosoftGraph Account takeover (nOAuth)","description":"### Summary\nThe 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](https://www.descope.com/blog/post/noauth) misconfiguration in cases when the `email` is used as a trusted user identifier\n","status":"published","published":"2024-01-03T21:46:46Z","modified":"2026-09-10T03:50:04.82998304Z","cvss":[{"version":"3.1","score":8.6,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L","level":"high"}],"cwes":["CWE-287"],"updated_at":"2026-11-02T15:46:38.213481Z"}]}}