Merative Merge DICOM Toolkit C++ up to 5.17.0 on Windows DICOM XML File MC_XML_To_Message memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.6 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Merative Merge DICOM Toolkit C++ up to 5.17.0 on Windows. The affected element is the function MC_XML_To_Message of the component DICOM XML File Handler. The manipulation leads to memory corruption.
This vulnerability is documented as CVE-2024-23913. The attack needs to be performed locally. There is not any exploit available.
Details
A vulnerability was found in Merative Merge DICOM Toolkit C++ up to 5.17.0 on Windows. It has been rated as problematic. This issue affects the function MC_XML_To_Message of the component DICOM XML File Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is availability. The summary by CVE is:
Use of Out-of-range Pointer Offset vulnerability in Merge DICOM Toolkit C/C++ on Windows. When deprecated MC_XML_To_Message() function is used to read a malformed DICOM XML file, it might result in memory access violation.
The weakness was released by Gabriele Quagliarella. The advisory is shared at nozominetworks.com. The identification of this vulnerability is CVE-2024-23913 since 01/23/2024. The exploitation is known to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.6VulDB Meta Temp Score: 3.6
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 4.0
CNA Vector: 🔍
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: Not defined
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/23/2024 🔍05/03/2024 🔍
05/03/2024 🔍
05/03/2024 🔍
Sources
Advisory: nozominetworks.comResearcher: Gabriele Quagliarella
Status: Not defined
CVE: CVE-2024-23913 (🔍)
GCVE (CVE): GCVE-0-2024-23913
GCVE (VulDB): GCVE-100-262961
Entry
Created: 05/03/2024 10:36Changes: 05/03/2024 10:36 (64)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.