Code execution via evaluated DICOM coordinates
Published Aug 23, 2024 · Updated Feb 13, 2026
Code injection in InVesalius 3.1.99991 through 3.1.99998 allows context-dependent attackers to execute code via a crafted DICOM file. GetImagePosition in invesalius/reader/dicom.py splits DICOM Image Position data and passes each untrusted coordinate to Python eval(). A victim must import the file; injected Python runs with the victim's application privileges without necessarily crashing or visibly disrupting the client.
Summary
What happened
Code injection in InVesalius 3.1.99991 through 3.1.99998 allows context-dependent attackers to execute code via a crafted DICOM file. GetImagePosition in invesalius/reader/dicom.py splits DICOM Image Position data and passes each untrusted coordinate to Python eval(). A victim must import the file; injected Python runs with the victim's application privileges without necessarily crashing or visibly disrupting the client.
The record
- CVE
- CVE-2024-42845
- Published
- Aug 23, 2024
- Updated
- Feb 13, 2026
- Vendor
- Centro de Tecnologia da Informação Renato Archer
- Product
- InVesalius
- Classifications
- CWE-94, T1204.002, T1059.006
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 23, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.1.99991 <=3.1.99998
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- InVesalius3 crafted DICOM proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo