Arbitrary file write via unchecked tar paths
Published Sep 25, 2024 · Updated Feb 13, 2026
Path traversal in InVesalius 3.1.99995 allows attackers to write arbitrary files by supplying a crafted .inv3 project archive. The Extract function in invesalius/project.py joins each untrusted tar member name to the temporary extraction directory without rejecting parent-path components. The file must be imported or opened by the desktop client; successful traversal writes attacker-chosen content with the user's file permissions.
Summary
What happened
Path traversal in InVesalius 3.1.99995 allows attackers to write arbitrary files by supplying a crafted .inv3 project archive. The Extract function in invesalius/project.py joins each untrusted tar member name to the temporary extraction directory without rejecting parent-path components. The file must be imported or opened by the desktop client; successful traversal writes attacker-chosen content with the user's file permissions.
The record
- CVE
- CVE-2024-44825
- Published
- Sep 25, 2024
- Updated
- Feb 13, 2026
- Vendor
- Centro de Tecnologia da Informação Renato Archer
- Product
- InVesalius
- Classifications
- CWE-22, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 25, 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.99995
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
- InVesalius 3.1 arbitrary-file-write proof of conceptproof of concept · demonstrated
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