mitmproxy pdoc up to 14.5.0 polyfill.io vulnerable third-party component
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in mitmproxy pdoc up to 14.5.0. This affects an unknown function of the component polyfill.io Handler. The manipulation results in vulnerable third-party component. This vulnerability is identified as CVE-2024-38526. The attack can be executed remotely. There is not any exploit available. The affected component should be upgraded.
Details
A vulnerability, which was classified as problematic, was found in mitmproxy pdoc up to 14.5.0. Affected is an unknown part of the component polyfill.io Handler. The manipulation with an unknown input leads to a vulnerable third-party component vulnerability. CWE is classifying the issue as CWE-1395. The product has a dependency on a third-party component that contains one or more known vulnerabilities. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
pdoc provides API Documentation for Python Projects. Documentation generated with `pdoc --math` linked to JavaScript files from polyfill.io. The polyfill.io CDN has been sold and now serves malicious code. This issue has been fixed in pdoc 14.5.1.
The advisory is available at github.com. This vulnerability is traded as CVE-2024-38526 since 06/18/2024. The exploitability is told to be difficult. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. The technical details are unknown and an exploit is not available.
The vulnerability scanner Nessus provides a plugin with the ID 212710 (Pdoc Python Library <= 14.5.1 (CVE-2024-38526)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 14.5.1 eliminates this vulnerability. Applying a patch 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.
The vulnerability is also documented in the vulnerability database at Tenable (212710). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
Website
- Product: https://github.com/mitmproxy/pdoc/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.2
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: Vulnerable third-party componentCWE: CWE-1395
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 |
Nessus ID: 212710
Nessus Name: Pdoc Python Library <= 14.5.1 (CVE-2024-38526)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: pdoc 14.5.1
Patch: github.com
Timeline
06/18/2024 🔍06/26/2024 🔍
06/26/2024 🔍
12/13/2024 🔍
Sources
Product: github.comAdvisory: GHSA-5vgj-ggm4-fg62
Status: Confirmed
CVE: CVE-2024-38526 (🔍)
GCVE (CVE): GCVE-0-2024-38526
GCVE (VulDB): GCVE-100-269706
Entry
Created: 06/26/2024 07:04Updated: 12/13/2024 03:26
Changes: 06/26/2024 07:04 (66), 06/27/2024 12:16 (1), 12/13/2024 03:26 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.