CVE-2024-22100
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 · uneditedMicroDicom DICOM Viewer versions 2023.3 (Build 9342) and prior are affected by a heap-based buffer overflow vulnerability, which could allow an attacker to execute arbitrary code on affected installations of DICOM Viewer. A user must open a malicious DCM file in order to exploit the vulnerability.
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 confidenceMicroDicom DICOM Viewer contains a heap-based buffer overflow vulnerability in its DCM file parsing logic. When a user opens a specially crafted malicious DCM file, the insufficient bounds checking during parsing allows an attacker to overflow heap memory, potentially achieving arbitrary code execution with the user's privileges.
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< 2024.1CVSS 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.
-
Check if Microdicom DICOM Viewer is installedLook for Microdicom DICOM Viewer in the list of installed applications via the system control panel or program files directoryAffected if The application is not found on the system, then the user is not affected by this specific vulnerability
-
Identify the installed version of Microdicom DICOM ViewerRight-click the application executable, select Properties, and view the version information on the Details tab, or check the application's About/Help sectionAffected if Version information cannot be determined, proceed with additional verification
-
Compare the installed version against the affected rangeCompare your installed version number to the known affected range: any version lower than 2024.1 is vulnerableAffected if The installed version is 2024.0 or any earlier version (such as 2023.x, 2022.x, etc.)
-
Determine if DCM file parsing is accessibleVerify that the application can open DCM files - the vulnerability is triggered when the application parses a specially crafted DCM fileAffected if The application is installed and capable of opening DCM files, the parsing logic is in use
If Microdicom DICOM Viewer is installed with a version lower than 2024.1, the environment is affected by this heap-based buffer overflow vulnerability in DCM file parsing.
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 · scoped2024.1
Do not open untrusted or unknown DCM files with MicroDicom DICOM Viewer. Monitor vendor for available patches and apply them promptly. Consider using file sanitization or sandboxing for viewing external DICOM files.
2024.1
- Check current installed version of MicroDicom DICOM Viewer
- Download version 2024.1 from the official MicroDicom website
- Uninstall the current vulnerable version (2023.3 or earlier)
- Install the updated version 2024.1
- Verify the installation by checking the version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-22100 — 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-2024-22100 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