dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-42845

HIGH · 8.0 CVSS v3.1 Published 2024-08-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An eval Injection vulnerability exists in the DICOM file reader component (invesalius/reader/dicom.py) of InVesalius versions 3.1.99991 through 3.1.99998. The vulnerability allows arbitrary code execution by loading a crafted DICOM file, likely due to unsafe use of Python's eval() function on DICOM field data.

MitigationReplace unsafe eval() calls in the DICOM parser with safe parsing methods (e.g., ast.literal_eval for literals, or structured parsing libraries). Validate and sanitize all DICOM field data before processing.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check InVesalius version
    Run 'pip show invesalius3' or check the application's About/Help section for the version number
    Affected if The version is 3.1.99991 through 3.1.99998 (inclusive)
  2. Locate the DICOM reader file
    Find the file 'reader/dicom.py' within the InVesalius installation directory - common paths include /usr/share/invesalius/ or the Python site-packages folder
    Affected if The file exists in the expected location within the InVesalius installation
  3. Inspect for unsafe eval() usage
    Open the dicom.py file and search for 'eval(' calls, particularly those processing DICOM field data or tag values
    Affected if The file contains eval() calls used on DICOM tag data without safe parsing methods
  4. Verify DICOM import functionality
    Attempt to load a DICOM file using InVesalius import or file open functionality
    Affected if The application can load DICOM files and processes them through the vulnerable reader component

A user is affected if they are running InVesalius versions 3.1.99991 through 3.1.99998 and use the DICOM file loading feature with the vulnerable eval() implementation present in the reader/dicom.py file.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace unsafe eval() calls in the DICOM parser with safe parsing methods (e.g., ast.literal_eval for literals, or structured parsing libraries). Validate and sanitize all DICOM field data before processing.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,896.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-42845 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-42845 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data