dbcve.org
Dicom EditorApplication · Santesoft

CVE-2023-32134

HIGH · 8.8 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 7.8.12 / 11.8.12 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Sante DICOM Viewer Pro DCM File Parsing Use-After-Free Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Sante DICOM Viewer Pro. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of DCM images. The issue results from the lack of validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-15629.

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

A use-after-free vulnerability exists in Sante DICOM Viewer Pro's DCM image parsing. The software fails to validate the existence of an object before performing operations on it, allowing an attacker to execute arbitrary code via a malicious DCM file. User interaction is required (opening a malicious file).

MitigationAvoid opening untrusted DCM files from unknown sources. Keep the software updated once a patch is available. Users should not open DCM files from untrusted sources or visit untrusted web pages.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Dicom EditorApplication
Affected:< 7.8.12
Dicom Viewer ProApplication
Affected:< 11.8.12

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify installed Santesoft DICOM product
    Check the application name in your installed programs list (Add/Remove Programs on Windows) - look for either 'Santesoft Dicom Editor' or 'Santesoft Dicom Viewer Pro'
    Affected if Either product is installed, proceed to version check
  2. Check installed version of Santesoft Dicom Editor
    If Dicom Editor is installed, open it and go to Help > About, or check the program's version property in Windows Programs and Features. Note the full version number (e.g., 7.8.11)
    Affected if Version is 7.8.11 or lower (less than 7.8.12)
  3. Check installed version of Santesoft Dicom Viewer Pro
    If Dicom Viewer Pro is installed, open it and go to Help > About, or check the program's version property in Windows Programs and Features. Note the full version number (e.g., 11.8.11)
    Affected if Version is 11.8.11 or lower (less than 11.8.12)
  4. Verify DCM file handling capability
    Confirm the software can open .DCM files - check if the application has file open dialogs with DCM filter or displays DCM in supported file type lists
    Affected if DCM file handling is available, the parsing vulnerability is reachable

You are affected if either Santesoft Dicom Editor version < 7.8.12 or Santesoft Dicom Viewer Pro version < 11.8.12 is installed and the software can open DCM files.

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.

dbcve · scoped
Upgrade available Upgrade to 7.8.12 / 11.8.12 or later
Fixed in 7.8.1211.8.12
Interim mitigation

Avoid opening untrusted DCM files from unknown sources. Keep the software updated once a patch is available. Users should not open DCM files from untrusted sources or visit untrusted web pages.

Recommended fix High confidence

Dicom Editor: 7.8.12 | Dicom Viewer Pro: 11.8.12

  1. Identify which Sante product is in use: Dicom Editor or Dicom Viewer Pro
  2. Check the current version of the installed software (typically in Help > About)
  3. If using Dicom Editor, upgrade to version 7.8.12 or later
  4. If using Dicom Viewer Pro, upgrade to version 11.8.12 or later
  5. Obtain the update from the official vendor website or trusted distribution channel
  6. Restart the application after upgrading
  7. Verify the installed version matches the fixed release

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dicom Editor Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32134 — 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-2023-32134 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