Safeguard
Vulnerability Analysis•

CVE-2023-32132: High DCM Out-of-Bounds Write in Sante Viewer

CVE-2023-32132 is a high (CVSS 8.8) out-of-bounds write in Sante DICOM Viewer Pro DCM parsing. Update to Viewer Pro 11.8.12 or Editor 7.8.12.

Safeguard Security Team
4 min read

CVE-2023-32132 is a high severity out-of-bounds write, scored 8.8, in Sante DICOM Viewer Pro. It is a second DCM parsing bug alongside CVE-2023-32131, and a crafted file can run code. ZDI says the fixed releases are Viewer Pro 11.8.12 and DICOM Editor 7.8.12.

What's affected

The NVD record, dated 2024-05-03, describes a flaw in the way Sante DICOM Viewer Pro parses DCM images. The weakness is CWE-787 (out-of-bounds write). The record's product list covers Sante DICOM Viewer Pro and Sante DICOM Editor. The record vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, scored 8.8.

The Zero Day Initiative advisory ZDI-23-524 (tracked as ZDI-CAN-15627) says crafted data in a DCM image can trigger a write past the end of an allocated buffer, which lets an attacker run code in the context of the current process. It also gives the fix: the issue is fixed in Sante DICOM Editor 7.8.12 and Sante DICOM Viewer Pro 11.8.12. The coordinated public release was on 2023-05-04, after the vendor was told in June 2022.

The sources disagree on severity. The NVD record says 8.8 with a network attack vector. ZDI scores the same flaw 7.8 with a local attack vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). The difference is the attack vector. In both cases a person must open a crafted file or visit a malicious page, and the impact on confidentiality, integrity and availability is high. No source says it is exploited in the wild, and it is not in the CISA catalog.

How to check if you're exposed

Open the application, go to its About dialog and read the version. Anything earlier than DICOM Viewer Pro 11.8.12 or DICOM Editor 7.8.12 is affected, according to ZDI.

Then ask where DICOM files come from. Imaging files arrive from modalities, from patient discs, by email and through file shares. Any workstation that opens files from outside your trusted network deserves priority, particularly shared reading stations and machines used by outside clinicians.

The same version fix covers the other flaws in this family. Updating once clears them all.

What to do now

  1. Find every machine with Sante DICOM Viewer Pro or Sante DICOM Editor installed.
  2. Update Viewer Pro to 11.8.12 or later, and Editor to 7.8.12 or later.
  3. Until updated, do not open DICOM files from untrusted sources on these machines.
  4. Keep imaging workstations off general web browsing and email where possible.
  5. Run the viewer as a standard user rather than as an administrator.
  6. Add the viewer to the endpoint software inventory so the next update is not missed.

Why it matters

This is the second of two DCM parsing write bugs that ZDI reported separately. They share a class, CWE-787, and a description, but ZDI tracks them as different flaws (ZDI-CAN-15626 and ZDI-CAN-15627) because they sit in different code paths. Fixing one does not guarantee the other is fixed, which is why you should update to the vendor build that names all of them rather than patching piecemeal. The advisory says an attacker who succeeds can run code in the context of the current process, so the damage depends on the account that is running the viewer. On a clinical workstation that account often reaches patient data. Safeguard offers a free in-browser dependency scan at gold.safeguard.sh/scan for the packages in your own code. It does not inspect installed desktop applications, so those need a manual inventory.

Quick check

How is this different from CVE-2023-32131?

Both are DCM out-of-bounds writes with identical descriptions and scores. ZDI tracks them under separate identifiers, ZDI-CAN-15626 and ZDI-CAN-15627, so they are separate defects. One update fixes both.

Is there a workaround?

The advisory does not give one. Update, and avoid opening DICOM files from untrusted sources until you do.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.