synth omniauth-microsoft_graph up to 1.x email improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical was found in synth omniauth-microsoft_graph up to 1.x. Affected by this issue is some unknown functionality. Such manipulation of the argument email leads to improper authentication. This vulnerability is documented as CVE-2024-21632. The attack can be executed remotely. There is not any exploit available. Upgrading the affected component is advised.
Details
A vulnerability, which was classified as critical, has been found in synth omniauth-microsoft_graph up to 1.x. Affected by this issue is an unknown function. The manipulation of the argument email with an unknown input leads to a improper authentication vulnerability. Using CWE to declare the problem leads to CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. Impacted is confidentiality, integrity, and availability. CVE summarizes:
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.
The weakness was released 01/03/2024 as GHSA-5g66-628f-7cvj. The advisory is shared for download at github.com. This vulnerability is handled as CVE-2024-21632 since 12/29/2023. There are known technical details, but no exploit is available.
Upgrading to version 2.0.0 eliminates this vulnerability. Applying the patch f132078389612b797c872b45bd0e0b47382414c1 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.6VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 8.6
CNA Vector (GitHub, Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: omniauth-microsoft_graph 2.0.0
Patch: f132078389612b797c872b45bd0e0b47382414c1
Timeline
12/29/2023 🔍01/03/2024 🔍
01/03/2024 🔍
01/23/2024 🔍
Sources
Product: github.comAdvisory: GHSA-5g66-628f-7cvj
Status: Confirmed
CVE: CVE-2024-21632 (🔍)
GCVE (CVE): GCVE-0-2024-21632
GCVE (VulDB): GCVE-100-249536
Entry
Created: 01/03/2024 09:04Updated: 01/23/2024 08:48
Changes: 01/03/2024 09:04 (53), 01/23/2024 08:48 (11)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.