InVesalius up to 3.1.99998 DICOM File dicom.py injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in InVesalius up to 3.1.99998. It has been classified as problematic. This vulnerability affects unknown code of the file invesalius/reader/dicom.py of the component DICOM File Handler. This manipulation causes injection. This vulnerability is tracked as CVE-2024-42845. The attack is restricted to local execution. Moreover, an exploit is present.
Details
A vulnerability classified as problematic was found in InVesalius up to 3.1.99998. Affected by this vulnerability is an unknown code block of the file invesalius/reader/dicom.py of the component DICOM File Handler. The manipulation with an unknown input leads to a injection vulnerability. The CWE definition for the vulnerability is CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
An eval Injection vulnerability in the component invesalius/reader/dicom.py of InVesalius 3.1.99991 through 3.1.99998 allows attackers to execute arbitrary code via loading a crafted DICOM file.
This vulnerability is known as CVE-2024-42845 since 08/05/2024. The exploitation appears to be easy. Attacking locally is a requirement. Technical details and also a public exploit are known. The attack technique deployed by this issue is T1055 according to MITRE ATT&CK.
It is possible to download the exploit at packetstormsecurity.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at 0day.today (39736). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.1VulDB Meta Temp Score: 6.9
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 8.0
CNA Vector (MITRE): 🔍
ADP CISA Base Score: 8.0
ADP CISA Vector: 🔍
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: InjectionCWE: CWE-74 / CWE-707 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
0day.today: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
08/05/2024 🔍08/23/2024 🔍
08/23/2024 🔍
02/13/2026 🔍
Sources
Status: Not definedCVE: CVE-2024-42845 (🔍)
GCVE (CVE): GCVE-0-2024-42845
GCVE (VulDB): GCVE-100-275707
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 08/23/2024 20:40Updated: 02/13/2026 18:41
Changes: 08/23/2024 20:40 (51), 08/26/2024 15:19 (1), 08/26/2024 17:52 (10), 08/28/2024 21:53 (1), 08/29/2024 09:46 (11), 02/13/2026 18:41 (13)
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.