CVE-2024-21632

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure.

Exploit odds

0.9% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2024-01-02 22:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 07:09 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.9% in the next 30 days (EPSS).
• Severity: 8.6 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2024-01-02 22:15 UTC

Last modified

2026-06-17 07:09 UTC

Exploit probability

0.9% · EPSS, next 30 days

Weakness

CWE-287 · Improper authentication

Record status

Modified

Affected

• Recognizeapp omniauth\ < 2.0.0

Attack profile CVSS 3.1 · 8.6

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

Low

Availability

Low

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2024-21632.md and follow it. Check whether this project is affected by CVE-2024-21632. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge