CVE-2022-24063
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 · uneditedThis 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 proper validation of user-supplied data, which can result in a memory corruption condition. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-15105.
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 confidenceA memory corruption vulnerability exists in Sante DICOM Viewer Pro's JP2 (JPEG 2000) file parsing logic. The application fails to properly validate user-supplied data during JP2 file processing, allowing an attacker to trigger memory corruption and achieve arbitrary code execution through a maliciously crafted JP2 file.
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< 11.9.2CVSS 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 installed Sante DICOM Viewer Pro versionOpen the application and navigate to Help > About, or check Add/Remove Programs (Windows) or the application's installation directory for version information. Compare the version number to 11.9.2.Affected if The installed version is lower than 11.9.2 (for example, 11.9.1, 11.8.x, etc.)
-
Verify JP2 file association or handling capabilityCheck if the application is configured to handle .jp2 or JPEG 2000 files. Look in the application's File > Open dialog or Preferences > File Types to see if JP2 is listed as a supported format.Affected if JP2 file handling is enabled and the application can open .jp2 files from the file menu or drag-and-drop.
-
Confirm JP2 processing is possibleSearch the application directories for JP2-related DLLs or codecs (such as j2k, jp2, or JPEG2000 in filenames), or check the application's documentation or preferences for enabled image processing modules.Affected if JPEG 2000/JP2 decoding libraries or plugins are present and loaded by the application.
A user is affected if Sante DICOM Viewer Pro version is below 11.9.2 AND the application is configured to process or open JP2 files from any source.
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 · scoped11.9.2
Update Sante DICOM Viewer Pro to a patched version. Until then, instruct users to avoid opening JP2 files from untrusted sources and disable automatic file handling where possible.
Sante DICOM Viewer Pro 11.9.2 or later
- Obtain Sante DICOM Viewer Pro version 11.9.2 or later from the official vendor (Sante)
- Backup any existing DICOM datasets and application settings before upgrading
- Uninstall the current version of Sante DICOM Viewer Pro
- Install the updated version (11.9.2 or later) from the official vendor distribution
- Verify the installation completed successfully
- Exercise caution when opening JP2 files from untrusted sources, even after patching
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24063 — 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-2022-24063 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