dbcve.org
Dicom Viewer ProApplication · Santesoft

CVE-2023-35986

HIGH · 7.8 CVSS v3.1 Published 2023-10-19
Fix available
A fix is available. Upgrade to 12.2.6 or later.
See remediation →
81/100
Remediation priority · High
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 lacks proper validation of user-supplied data when parsing DICOM files. This could lead to a stack-based buffer overflow. An attacker could leverage this vulnerability to execute arbitrary code in the context of the current process.

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 · moderate confidence

Sante DICOM Viewer Pro fails to validate user-supplied data during DICOM file parsing, allowing a stack-based buffer overflow. An attacker can craft a malicious DICOM file to overwrite stack memory and achieve arbitrary code execution within the application's context.

MitigationImplement rigorous bounds checking and input validation in the DICOM file parsing routines; apply any vendor-provided patches; consider restricting DICOM file sources to trusted files until patch is applied.

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 Viewer ProApplication
Affected:< 12.2.6

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

CVSS:3.1/AV:L/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. Locate the installed Sante DICOM Viewer Pro application
    Check the program's About/Help menu, or find the executable in the installation directory (commonly C:\Program Files\Santesoft\DICOM Viewer Pro\) and view its properties to find the version number
    Affected if The version displayed is below 12.2.6 (for example, 12.2.5, 12.2.0, or earlier)
  2. Verify the exact version number in program files
    Navigate to the installation folder, right-click the main executable (often named something like DICOMViewerPro.exe), select Properties, and read the File Version on the Details tab
    Affected if The version starts with a number lower than 12.2.6, such as 12.2.5 or any 12.x version below 12.2.6
  3. Confirm DICOM file handling is used
    Determine whether the application is used to open, view, or process DICOM files from external or untrusted sources
    Affected if The application is used to parse DICOM files, as the vulnerability is triggered during DICOM file parsing
  4. Review recent file open activity
    Check application logs or recent files list for DICOM files that may have been opened from untrusted sources
    Affected if DICOM files from untrusted or external sources have been opened in the application

If the installed Sante DICOM Viewer Pro version is below 12.2.6 and you open DICOM files with it, your environment is likely affected by this buffer overflow vulnerability.

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 12.2.6 or later
Fixed in 12.2.6
Interim mitigation

Implement rigorous bounds checking and input validation in the DICOM file parsing routines; apply any vendor-provided patches; consider restricting DICOM file sources to trusted files until patch is applied.

Recommended fix High confidence

Sante DICOM Viewer Pro 12.2.6 or later

  1. Obtain Sante DICOM Viewer Pro version 12.2.6 or later from the official vendor website or authorized distribution channel
  2. Backup any important data, configurations, or custom settings from the current installation
  3. Uninstall the current (vulnerable) version of Sante DICOM Viewer Pro
  4. Install version 12.2.6 or later of Sante DICOM Viewer Pro
  5. Restore any backed up data or custom configurations
  6. Launch the application and verify it runs without errors

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

Fix this in Dicom Viewer Pro Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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