adolph_dudu ratio-swiper 0.0.2 parse prototype pollution
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in adolph_dudu ratio-swiper 0.0.2. It has been rated as problematic. This vulnerability affects the function parse. The manipulation leads to prototype pollution.
This vulnerability is listed as CVE-2024-39000. There is no available exploit.
This entry seems to have a duplicate CVE-2024-39853 assigned.
Details
A vulnerability was found in adolph_dudu ratio-swiper 0.0.2. It has been rated as problematic. This issue affects the function parse. The manipulation with an unknown input leads to a prototype pollution vulnerability. Using CWE to declare the problem leads to CWE-1321. The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
adolph_dudu ratio-swiper v0.0.2 was discovered to contain a prototype pollution via the function parse. This vulnerability allows attackers to execute arbitrary code or cause a Denial of Service (DoS) via injecting arbitrary properties.
The advisory is shared at gist.github.com. The identification of this vulnerability is CVE-2024-39000 since 06/21/2024. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Prototype pollutionCWE: CWE-1321 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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
06/21/2024 🔍07/01/2024 🔍
07/01/2024 🔍
07/08/2025 🔍
Sources
Advisory: gist.github.comStatus: Not defined
CVE: CVE-2024-39000 (🔍)
CVE Duplicate: 🔍
GCVE (CVE): GCVE-0-2024-39000
GCVE (VulDB): GCVE-100-270053
Entry
Created: 07/01/2024 16:14Updated: 07/08/2025 01:11
Changes: 07/01/2024 16:14 (51), 07/01/2024 16:20 (1), 07/08/2025 01:11 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.