Memory exhaustion via unreleased file-information allocations
Published Jun 28, 2022 · Updated Nov 3, 2025
Memory exhaustion in DCMTK dcmqrdb through 3.6.6 allows remote attackers to interrupt the service through crafted DICOM requests. The program retains heap allocations for file information in the global LST variable instead of releasing them after processing affected requests. Repeated unauthenticated network requests consume process memory until dcmqrdb becomes unavailable, without reported data disclosure or modification.
Summary
What happened
Memory exhaustion in DCMTK dcmqrdb through 3.6.6 allows remote attackers to interrupt the service through crafted DICOM requests. The program retains heap allocations for file information in the global LST variable instead of releasing them after processing affected requests. Repeated unauthenticated network requests consume process memory until dcmqrdb becomes unavailable, without reported data disclosure or modification.
The record
- CVE
- CVE-2021-41690
- Published
- Jun 28, 2022
- Updated
- Nov 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 28, 2022CVE publishedPublication date reported by the CVE source.
- Nov 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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