CVE-2023-32133 is a high severity out-of-bounds write, scored 8.8, in the way Sante DICOM Viewer Pro parses J2K (JPEG 2000) images. A crafted image can run code when someone opens it. ZDI says Sante DICOM Viewer Pro 11.8.12 and DICOM Editor 7.8.12 contain the fix, so update both.
What's affected
The NVD record, dated 2024-05-03, describes a flaw in the way Sante DICOM Viewer Pro parses J2K 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-525 (tracked as ZDI-CAN-15628) says crafted data in a J2K 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
- Find every machine with Sante DICOM Viewer Pro or Sante DICOM Editor installed.
- Update Viewer Pro to 11.8.12 or later, and Editor to 7.8.12 or later.
- Until updated, do not open DICOM files from untrusted sources on these machines.
- Keep imaging workstations off general web browsing and email where possible.
- Run the viewer as a standard user rather than as an administrator.
- Add the viewer to the endpoint software inventory so the next update is not missed.
Why it matters
Unlike its two siblings, this one is in J2K handling, not DCM. J2K is JPEG 2000 compressed image data, a format DICOM files can carry. The weakness is CWE-787, a write past the end of a reserved buffer. 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.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
What is J2K?
J2K is the JPEG 2000 image format. The ZDI advisory says the flaw is in how the viewer parses J2K images.
Do I need a separate patch for this one?
No. ZDI says the issue is fixed in DICOM Viewer Pro 11.8.12 and DICOM Editor 7.8.12, the same builds that fix the DCM bugs.
Sources
Last reviewed: 19 October 2026.