| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in MongoDB Compass up to 1.40.5. It has been classified as problematic. Affected is an unknown function. This manipulation causes event data. This vulnerability is handled as CVE-2024-3371. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability has been found in MongoDB Compass up to 1.40.5 and classified as problematic. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a event data vulnerability. The CWE definition for the vulnerability is CWE-360. Security based on event locations are insecure and can be spoofed. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
MongoDB Compass may accept and use insufficiently validated input from an untrusted external source. This may cause unintended application behavior, including data disclosure and enabling attackers to impersonate users. This issue affects MongoDB Compass versions 1.35.0 to 1.40.5.
It is possible to read the advisory at jira.mongodb.org. This vulnerability is known as CVE-2024-3371 since 04/05/2024. The exploitation appears to be difficult. The attack can be launched remotely. The technical details are unknown and an exploit is not publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.0
VulDB Temp Score: 5.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.8
NVD Vector: 🔍
CNA Base Score: 7.1
CNA Vector (MongoDB, 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: Event dataCWE: CWE-360
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
04/05/2024 🔍04/24/2024 🔍
04/24/2024 🔍
02/07/2025 🔍
Sources
Advisory: jira.mongodb.orgStatus: Confirmed
CVE: CVE-2024-3371 (🔍)
GCVE (CVE): GCVE-0-2024-3371
GCVE (VulDB): GCVE-100-261931
Entry
Created: 04/24/2024 18:57Updated: 02/07/2025 04:48
Changes: 04/24/2024 18:57 (60), 05/29/2024 09:24 (1), 02/07/2025 04:48 (12)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.