CVE-2024-21632: omniauth\ Auth Bypass

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.

Is your site exposed to CVE-2024-21632?

Run a free security scan — no signup, results in seconds.

CVSS v3.1 Score

8.6

HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

Weakness Type (CWE)

CWE-287 Improper Authentication

Affected Products

Vendor	Product	Versions
recognizeapp	omniauth\	< 2.0.0

References

Advisories & Patches

https://github.com/synth/omniauth-microsoft_graph/commit/f132078389612b797c872b45bd0e0b47382414c1 https://github.com/synth/omniauth-microsoft_graph/security/advisories/GHSA-5g66-628f-7cvj https://github.com/synth/omniauth-microsoft_graph/commit/f132078389612b797c872b45bd0e0b47382414c1 https://github.com/synth/omniauth-microsoft_graph/security/advisories/GHSA-5g66-628f-7cvj

Exploits

https://www.descope.com/blog/post/noauth https://www.descope.com/blog/post/noauth

Frequently Asked Questions

What is CVE-2024-21632? +

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. It has a CVSS v3.1 base score of 8.6 (HIGH).

How severe is CVE-2024-21632? +

CVE-2024-21632 has a CVSS v3.1 score of 8.6 out of 10, rated HIGH. This is a high-severity vulnerability that should be prioritized for patching.

What products are affected by CVE-2024-21632? +

CVE-2024-21632 affects products from recognizeapp, specifically: omniauth\. Check the affected products table above for specific version ranges.

How do I check if I'm vulnerable to CVE-2024-21632? +

You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.

Related Vulnerabilities

CVE-2026-47202

Kavita is a cross platform reading server. Prior to 0.9.0.2, an Improper Token validation flaw permits a remote and unauthenticated …

CVE-2026-61740

LightRAG provides simple and fast retrieval-augmented generation. Prior to 1.5.4, when LightRAG is deployed with LIGHTRAG_API_KEY set but AUTH_ACCOUNTS unset, …

CVE-2026-47159

Vaultwarden is a Bitwarden-compatible server written in Rust. Prior to 1.36.0, Vaultwarden's SSO discovery and pre-validation flow returned organization-related SSO …

CVE-2026-44720

OpenLearnX is an open-source, decentralized learning and assessment platform. Prior to 2.0.4, a critical authentication vulnerability was identified in OpenLearnX …

CVE-2025-24032

PAM-PKCS#11 is a Linux-PAM login module that allows a X.509 certificate based user login. Prior to version 0.6.13, if cert_policy …

CVE-2024-5174

A flaw in Gliffy results in broken authentication through the reset functionality of the application.

CVE-2024-21632