Local memory corruption in mDicom.exe
Published Mar 6, 2025 · Updated Mar 6, 2025
Memory corruption in mDicom.exe in MicroDicom DICOM Viewer 2025.1 Build 3321 allows local users to corrupt process memory. The public disclosure identifies neither the vulnerable function nor the untrusted input and operation that trigger the corruption. Exploitation requires local low-privilege access; disclosed effects are confined to the affected process and its data.
Summary
What happened
Memory corruption in mDicom.exe in MicroDicom DICOM Viewer 2025.1 Build 3321 allows local users to corrupt process memory. The public disclosure identifies neither the vulnerable function nor the untrusted input and operation that trigger the corruption. Exploitation requires local low-privilege access; disclosed effects are confined to the affected process and its data.
The record
- CVE
- CVE-2025-2029
- Published
- Mar 6, 2025
- Updated
- Mar 6, 2025
- Vendor
- MicroDicom
- Product
- MicroDicom DICOM Viewer
- Classifications
- CWE-119
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 6, 2025CVE publishedPublication date reported by the CVE source.
- Mar 6, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2025.1 Build 3321
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo