CVE-2024-21632
January 02, 2024
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.
Affected Packages
omniauth-microsoft_graph (RUBY):
Affected version(s) >=0.1.0 <2.0.0Fix Suggestion:
Update to version 2.0.0Additional Notes
The description of this vulnerability differs from MITRE.
Related Resources (6)
Do you need more information?
Contact UsCVSS v4
Base Score:
8.8
Attack Vector
NETWORK
Attack Complexity
LOW
Attack Requirements
NONE
Privileges Required
NONE
User Interaction
NONE
Vulnerable System Confidentiality
HIGH
Vulnerable System Integrity
LOW
Vulnerable System Availability
LOW
Subsequent System Confidentiality
NONE
Subsequent System Integrity
NONE
Subsequent System Availability
NONE
CVSS v3
Base Score:
8.6
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
LOW
Availability
LOW
Weakness Type (CWE)
Improper Authentication
EPSS
Base Score:
0.31
