Lucene search
+L

5 matches found

Veracode
Veracode
•added 2024/01/03 7:55 a.m.•24 views

Improper Authentication

omniauth-microsoftgraph is vulnerable to Improper Authentication. The vulnerability is due to missing validation of the email attribute received from Microsoft's OAuth service. This allows an attacker to bypass the email verification in the OAuth process and takeover an account...

9.8CVSS6.8AI score0.00904EPSS
SaveExploits1References3Affected Software1
Cvelist
Cvelist
•added 2024/01/02 9:54 p.m.•82 views

CVE-2024-21632 omniauth-microsoft_graph vulnerable to account takeover (nOAuth)

omniauth-microsoftgraph 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...

8.6CVSS9.6AI score0.00904EPSS
SaveExploits1References3
CVE
CVE
•added 2024/01/02 9:54 p.m.•137 views

CVE-2024-21632

The CVE-2024-21632 entry concerns omniauth-microsoft_graph, an Omniauth strategy for Microsoft Graph. Before version 2.0.0, it did not validate the user email attribute (nor provided an option to do so), exposing risk of nOAuth misconfiguration when email is used as a trusted user identifier and ...

9.8CVSS9.2AI score0.00904EPSS
SaveExploits1References3Affected Software1
Mend
Mend
•added 2024/01/02 9:54 p.m.•2 views

CVE-2024-21632

omniauth-microsoftgraph 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 case...

9.8CVSS0.00904EPSS
SaveExploits1References7
Rapid7 Vulnerability Database (full)
Rapid7 Vulnerability Database (full)
•added 2024/01/02 12:00 a.m.•6 views

CVE-2024-21632: Improper Authentication

omniauth-microsoftgraph 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...

9.8CVSS8AI score0.00904EPSS
SaveExploits1References2
Rows per page
Query Builder