Auth bypass in Recognizeapp Omniauth\
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.
Vulnerability class: Broken Authentication
EPSS: 0.009 (56.1th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 8.6 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L.
Affected products
- Recognizeapp Omniauth\ — versions \
- Synth Omniauth-microsoft_graph — versions < 2.0.0
Weakness classification (CWE)
Public proof-of-concept exploits
References
- security-advisories@github.com (x_refsource_CONFIRM, Vendor Advisory)
- security-advisories@github.com (Patch, x_refsource_MISC)
- security-advisories@github.com (Exploit, x_refsource_MISC)
Frequently asked questions
- What is CVE-2024-21632?
- CVE-2024-21632 is a high-severity vulnerability in Recognizeapp Omniauth\, classified under Improper Authentication. CVSS score: 8.6/10. Published 2024-01-02.
- How severe is CVE-2024-21632?
- High severity. CVSS v3 base score is 8.6 out of 10.
- Is CVE-2024-21632 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.