CVE-2024-28877
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 is vulnerable to a stack-based buffer overflow, which may allow an attacker to execute arbitrary code on affected installations of DICOM Viewer. User interaction is required to exploit this 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 stack-based buffer overflow vulnerability in its DICOM file parsing functionality. An attacker can craft a malicious DICOM file that, when opened by a victim, overflows a stack buffer and allows arbitrary code execution. User interaction is required (the victim must open the malicious 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< 2024.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Determine installed MicroDicom versionOpen MicroDicom DICOM Viewer, navigate to Help > About, or right-click the executable (MicroDicom.exe) in Program Files and view Properties > Details to see the version numberAffected if The version listed is earlier than 2024.2 (for example, 2023.1, 2022.3, etc.)
-
Verify the viewer is used for DICOM filesConfirm that the system has the MicroDicom application installed and is used to open or view DICOM medical imaging filesAffected if The application is present and configured to parse DICOM files, making the parsing functionality active
-
Check for recent DICOM file handling activityReview recent file access logs or the application's recent files list to see if DICOM files have been opened recentlyAffected if DICOM files have been opened with this viewer, triggering the vulnerable parsing code path
-
Confirm patch status via vendorCheck MicroDicom's official website or release notes for version 2024.2 or later to confirm whether an update addressing this vulnerability is availableAffected if Version 2024.2 or later is not installed, meaning the vulnerability remains unpatched
You are affected if MicroDicom DICOM Viewer version is installed and is lower than 2024.2, and DICOM files can be opened with it (user interaction required for exploitation).
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.2
Apply any available vendor patch when released. Until then, enforce strict file handling policies: only open DICOM files from trusted sources, disable automatic file loading, and run the viewer in a sandboxed or least-privilege environment to limit impact of successful exploitation.
2024.2
- 1. Obtain the latest version of MicroDicom DICOM Viewer (version 2024.2 or later) from the official vendor source
- 2. Uninstall the current vulnerable version of MicroDicom DICOM Viewer
- 3. Install the updated version 2024.2 or later
- 4. Verify the installed version matches the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,248.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28877 — 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-28877 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