pyload-ng up to 0.5.0b3.dev85 HTTP Request privilege escalation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in pyload-ng up to 0.5.0b3.dev85. The affected element is an unknown function of the component HTTP Request Handler. The manipulation leads to an unknown weakness. This vulnerability is documented as CVE-2024-39205. Additionally, an exploit exists.
Details
A vulnerability was found in pyload-ng up to 0.5.0b3.dev85 and classified as problematic. This issue affects an unknown functionality of the component HTTP Request Handler. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
An issue in pyload-ng v0.5.0b3.dev85 running under python3.11 or below allows attackers to execute arbitrary code via a crafted HTTP request.
The identification of this vulnerability is CVE-2024-39205 since 06/21/2024. Technical details are unknown but a public exploit is available.
The exploit is available at packetstormsecurity.com. It is declared as highly functional.
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
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: Privilege escalationCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Access: Public
Status: Highly functional
Download: 🔍
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 🔍10/28/2024 🔍
10/28/2024 🔍
11/18/2024 🔍
Sources
Status: Not definedCVE: CVE-2024-39205 (🔍)
GCVE (CVE): GCVE-0-2024-39205
GCVE (VulDB): GCVE-100-282101
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 10/28/2024 22:12Updated: 11/18/2024 16:27
Changes: 10/28/2024 22:12 (50), 11/18/2024 16:27 (7)
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.