MicroDicom DICOM Viewer 2025.1 Build 3321 mDicom.exe memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in MicroDicom DICOM Viewer 2025.1 Build 3321. Affected is an unknown function of the file mDicom.exe. The manipulation results in memory corruption. This vulnerability is known as CVE-2025-2029. Attacking locally is a requirement. Furthermore, an exploit is available. The affected component should be upgraded. The vendor quickly confirmed the existence of the vulnerability and fixed it in the latest beta.
Details
A vulnerability was found in MicroDicom DICOM Viewer 2025.1 Build 3321. It has been classified as critical. Affected is an unknown part of the file mDicom.exe. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability.
This vulnerability is traded as CVE-2025-2029. The exploitability is told to be easy. Local access is required to approach this attack. Technical details and a exploit are known.
It is declared as proof-of-concept. The vendor quickly confirmed the existence of the vulnerability and fixed it in the latest beta.
Upgrading eliminates this vulnerability. The upgrade is hosted for download at microdicom.com.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Proof-of-Concept
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: microdicom.com
Timeline
03/06/2025 🔍03/06/2025 🔍
03/06/2025 🔍
Sources
Status: ConfirmedCVE: CVE-2025-2029 (🔍)
GCVE (CVE): GCVE-0-2025-2029
GCVE (VulDB): GCVE-100-298770
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/06/2025 09:40Changes: 03/06/2025 09:40 (54)
Complete: 🔍
Submitter: 0x20z
Cache ID: 216::103
Submit
Accepted
- Submit #506579: MicroDicom MicroDicomViewer 2025.1(Build3321) Memory Access Violation (by 0x20z)
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.