dbcve.org
Dicom Viewer ProApplication · Santesoft

CVE-2022-24062

HIGH · 7.8 CVSS v3.1 Published 2022-02-18
Fix available
A fix is available. Upgrade to 11.9.2 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
This vulnerability allows remote attackers to execute arbitrary code on affected installations of Sante DICOM Viewer Pro 13.2.0.21165. 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 JP2 files. 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-15104.

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

This is a memory corruption vulnerability in Sante DICOM Viewer Pro where the JP2 (JPEG 2000) file parser fails to validate that an object exists before performing operations on it, likely a null pointer dereference. An attacker can exploit this by tricking a user into opening a malicious JP2 file, allowing arbitrary code execution in the context of the current process.

MitigationUsers should avoid opening JP2 or DICOM files from untrusted sources. Organizations should deploy the vendor patch when available and consider network segmentation for systems running this viewer.

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:< 11.9.2

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. Verify if Sante DICOM Viewer Pro is installed
    Check Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'Sante DICOM Viewer Pro', or look for the executable in common installation paths such as C:\Program Files\Santesoft\DICOM Viewer Pro\
    Affected if The software is found on the system
  2. Determine the installed version number
    Open the application's main executable (typically SanteDICOMViewer.exe), right-click and select Properties, then check the Details tab for the Product Version field; alternatively, check the Uninstall registry key for the DisplayVersion value
    Affected if The version displayed is lower than 11.9.2 (for example, 11.9.1, 11.9.0, or earlier)
  3. Confirm JP2 file association with the viewer
    Check Windows file association settings for .jp2 files by running 'assoc .jp2' in Command Prompt, or look in the viewer's options/settings for enabled file type handlers
    Affected if The .jp2 file extension is associated with Sante DICOM Viewer Pro or JP2 parsing is enabled in the viewer settings
  4. Check for recent JP2 file activity
    Open the viewer's recent files or history feature (usually found in the File menu), or check the Windows Recent folder %APPDATA%\Santesoft\DICOM Viewer Pro\Recent for .jp2 entries
    Affected if Any JP2 files have been opened with this viewer, indicating the vulnerable code path could be triggered

You are affected if Sante DICOM Viewer Pro is installed with a version lower than 11.9.2 and the application is used to open JP2 image 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 11.9.2 or later
Fixed in 11.9.2
Interim mitigation

Users should avoid opening JP2 or DICOM files from untrusted sources. Organizations should deploy the vendor patch when available and consider network segmentation for systems running this viewer.

Recommended fix High confidence

11.9.2

  1. Check current version of Sante DICOM Viewer Pro by opening the application and navigating to Help > About or similar version information menu
  2. Download Sante DICOM Viewer Pro version 11.9.2 or later from the official vendor website or trusted distribution channel
  3. Close any running instances of Sante DICOM Viewer Pro
  4. Install the updated version 11.9.2 or newer over the existing installation, or uninstall the old version first before installing the new one
  5. Restart the application and verify the new version is installed correctly
  6. Avoid opening untrusted or suspicious JP2 files from unknown sources as a precautionary measure

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

Fix this in Dicom Viewer Pro Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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