CVE-2022-28668
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.9.2. 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. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of an allocated data structure. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-16679.
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 · moderate confidenceA buffer overflow vulnerability exists in Sante DICOM Viewer Pro 11.9.2 during J2K (JPEG 2000) file parsing. The lack of proper validation of user-supplied data allows writing past the end of an allocated buffer, enabling arbitrary code execution in the context of the current process. Exploitation requires user interaction—opening a malicious J2K 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.
-
Verify Sante DICOM Viewer Pro is installedCheck the system for Sante DICOM Viewer Pro installation. Common installation paths: C:\Program Files\Santesoft\ or look in Windows Add/Remove Programs. Also check for executable files named 'SanteViewer.exe' or similar Sante DICOM-related binaries.Affected if Sante DICOM Viewer Pro is not found on the system, then not affected.
-
Identify the installed version numberRight-click the Sante DICOM Viewer Pro executable, select Properties, then view the Details tab for Version Information. Alternatively, open the application and check Help > About. Record the exact version number.Affected if The installed version is exactly 11.9.2, then the environment is vulnerable to this specific CVE.
-
Confirm J2K file parsing capability is presentVerify that the installation includes J2K (JPEG 2000) decoding libraries. Check the application's supported file format list or look for J2K-related DLLs in the program directory (such as j2k_*.dll or similar).Affected if J2K parsing capability exists in the installed version, then the buffer overflow vulnerability can be triggered when processing malicious J2K files.
-
Review recent file activity for J2K inputsCheck application logs, recent documents, or file open history for any recently opened .j2k, .jp2, or JPEG 2000 files. This indicates the vulnerable parsing code path was executed.Affected if J2K files have been opened with this version, the vulnerability may have been triggered.
The environment is affected if Sante DICOM Viewer Pro version 11.9.2 is installed and J2K file parsing functionality is available or has been used.
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 files from unknown sources. Update to the vendor's patched version when available.
- Consultation1.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28668 — 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-28668 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