CVE-2023-39431
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 · uneditedSante DICOM Viewer Pro lacks proper validation of user-supplied data when parsing DICOM files. This could lead to an out-of-bounds write. 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 · high confidenceSante DICOM Viewer Pro fails to properly validate user-supplied data when parsing DICOM files, allowing malformed input to trigger an out-of-bounds write vulnerability. This memory corruption can be leveraged by an attacker to achieve arbitrary code execution within the context of the running process.
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< 12.2.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Sante DICOM Viewer Pro is installedCheck common installation paths: C:\Program Files\Santesoft\DICOM Viewer Pro\ or C:\Program Files (x86)\Santesoft\DICOM Viewer Pro\. Look for the application executable (DICOMViewerPro.exe) in these locations.Affected if The application is present on the system
-
Determine the installed versionRight-click on DICOMViewerPro.exe, select Properties, and view the Details tab for the File Version. Alternatively, open the application and navigate to Help > About to view the version information.Affected if The version number displayed is lower than 12.2.6
-
Confirm the vulnerability trigger conditionThis vulnerability is triggered during DICOM file parsing. Check whether the software is configured to automatically parse or preview DICOM files from external or untrusted sources.Affected if You process DICOM files from untrusted sources using this software and your version is below 12.2.6
You are affected if Sante DICOM Viewer Pro version 12.2.6 or higher is NOT installed AND you parse DICOM files with the software.
Generated from the published advisory. Verify against your own configuration.
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 · scoped12.2.6
Apply vendor-provided patches or updates to Sante DICOM Viewer Pro. Until patches are available, exercise extreme caution when opening DICOM files from untrusted sources, as the vulnerability can be triggered simply by parsing a specially crafted malicious DICOM file.
12.2.6 or later
- Backup all important DICOM data and files before proceeding with the upgrade
- Close any running instances of Sante DICOM Viewer Pro
- Download Sante DICOM Viewer Pro version 12.2.6 or later from the official vendor website (ensure you are downloading from a trusted source)
- Run the installer for version 12.2.6 as administrator
- Follow the on-screen installation prompts to complete the upgrade
- Restart the application after installation completes
- Verify the installed version is 12.2.6 or later by checking About or Help > Version information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-39431 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-39431 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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