Application crash via malformed DICOM XML parsing
Published May 3, 2024 · Updated Dec 6, 2024
Out-of-range pointer use in Merative Merge DICOM Toolkit C/C++ 5.0.0 through 5.17.0 allows local users to crash an application. The deprecated MC_XML_To_Message function reads a malformed DICOM XML file and computes an out-of-range pointer offset, causing a memory access violation. The flaw is reachable when a Windows application linked with the affected 64-bit toolkit passes attacker-controlled XML to the deprecated function; the bounded impact is an application crash.
Summary
What happened
Out-of-range pointer use in Merative Merge DICOM Toolkit C/C++ 5.0.0 through 5.17.0 allows local users to crash an application. The deprecated MC_XML_To_Message function reads a malformed DICOM XML file and computes an out-of-range pointer offset, causing a memory access violation. The flaw is reachable when a Windows application linked with the affected 64-bit toolkit passes attacker-controlled XML to the deprecated function; the bounded impact is an application crash.
The record
- CVE
- CVE-2024-23913
- Published
- May 3, 2024
- Updated
- Dec 6, 2024
- Vendor
- Merative
- Product
- Merge DICOM Toolkit C/C++
- Classifications
- CWE-823, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 3, 2024CVE publishedPublication date reported by the CVE source.
- Dec 6, 2024Record 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=v5.0.0 <=v5.17.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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