CVE-2022-24057
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 11.8.7.0. 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 J2K files. Crafted data in a J2K file can trigger a write past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-15077.
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 confidenceBuffer overflow vulnerability in Sante DICOM Viewer Pro's J2K file parser. Attackers can craft malicious J2K files that trigger a write past the end of an allocated buffer during parsing, allowing arbitrary code execution in the context of the current user 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= 11.8.7CVSS 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.
-
Verify Sante DICOM Viewer Pro is installedCheck for the presence of Sante DICOM Viewer Pro application in the system (typically in Program Files or Program Files x86). Look for executable files named similar to 'Sante DICOM Viewer Pro.exe' or check Windows Add/Remove Programs for the application.Affected if The application is not installed on the system, then this CVE does not apply.
-
Determine installed versionRight-click the application executable, select Properties, then view the Details tab for version information. Alternatively, check the application's About or Help menu for version details.Affected if The installed version is exactly 11.8.7, indicating the specific version affected by this CVE.
-
Identify J2K file handling capabilityExamine if the application has been configured to handle or process J2K (JPEG 2000) files. Check file association settings or application preferences for supported image formats.Affected if J2K file parsing is enabled or the application automatically processes J2K files embedded in DICOM images, making it vulnerable to crafted files.
-
Review recent DICOM file importsCheck the application\'s recent files list, import history, or designated DICOM folders for recently opened .dcm or .j2k files. Examine file sources to determine if any originated from untrusted sources.Affected if The application has recently opened DICOM or J2K files from untrusted or external sources, creating potential attack surface.
A system is affected only if Sante DICOM Viewer Pro version 11.8.7 is installed AND the system processes J2K or DICOM files containing J2K images.
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.
From vendor dataAvoid opening untrusted J2K or DICOM files. Apply vendor-supplied patches for Sante DICOM Viewer Pro when available. Consider file type validation and sandboxing for additional defense-in-depth.
- 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-24057 — 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-24057 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