CVE-2023-39431

7.8 HIGH

📋 TL;DR

CVE-2023-39431 is an out-of-bounds write vulnerability in Sante DICOM Viewer Pro due to improper validation of user-supplied DICOM files, allowing arbitrary code execution in the current process context. This affects users of the vulnerable software, particularly in healthcare and medical imaging environments where DICOM files are processed.

💻 Affected Systems

Products:
  • Sante DICOM Viewer Pro
Versions: Specific versions not detailed in provided references; assume all versions prior to patched release are vulnerable.
Operating Systems: Windows, Linux, macOS
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability is triggered when parsing malicious DICOM files, so any default configuration that processes such files is at risk.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

An attacker could execute arbitrary code with the privileges of the current user, potentially leading to full system compromise, data theft, or disruption of medical imaging operations.

🟠

Likely Case

Exploitation could result in remote code execution, enabling attackers to install malware, exfiltrate sensitive medical data, or pivot to other systems on the network.

🟢

If Mitigated

With proper controls like network segmentation and least privilege, impact may be limited to isolated systems or prevented if patches are applied promptly.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: HIGH

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: MEDIUM

Exploitation requires an attacker to supply a crafted DICOM file, which could be delivered via email, web, or network shares. No public proof-of-concept is known, but the vulnerability is critical and may be targeted.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check vendor advisory for specific patched version.

Vendor Advisory: https://www.cisa.gov/news-events/ics-medical-advisories/icsma-23-285-01

Restart Required: Yes

Instructions:

1. Review the CISA advisory for details. 2. Contact the vendor for the latest patched version. 3. Apply the patch to all affected systems. 4. Restart the application or system as required.

🔧 Temporary Workarounds

Restrict DICOM file sources

all

Limit processing of DICOM files to trusted sources only, such as internal networks or verified medical devices.

Use application whitelisting

windows

Implement application control to prevent unauthorized execution of code, reducing the impact of potential exploitation.

🧯 If You Can't Patch

  • Isolate affected systems on segmented networks to limit lateral movement.
  • Implement strict access controls and monitor for unusual file processing activities.

🔍 How to Verify

Check if Vulnerable:

Check the software version against the vendor's patched release; if using an older version, assume vulnerability.

Check Version:

Consult the software's help or about menu for version details; no universal command provided.

Verify Fix Applied:

Update to the patched version specified by the vendor and confirm no errors occur when parsing test DICOM files.

📡 Detection & Monitoring

Log Indicators:

  • Unexpected crashes or errors in Sante DICOM Viewer logs when processing files
  • Unusual process creation or network connections from the viewer

Network Indicators:

  • Inbound transfers of DICOM files from untrusted sources
  • Outbound connections to suspicious IPs post-file processing

SIEM Query:

Example: 'process_name:"Sante DICOM Viewer" AND event_type:crash' or 'file_type:DICOM AND source_ip:external'

🔗 References

📤 Share & Export