Service interruption via request-parsing memory leak
Published Jun 28, 2022 · Updated Nov 3, 2025
Memory leak in DCMTK dcmqrdb 3.6.6 and earlier allows remote attackers to exhaust memory and interrupt the service via crafted requests. Error paths in the dcmnet association parser leave heap-allocated presentation-context and user-information list entries unreleased after malformed data is rejected. Network access to a running dcmqrdb service is sufficient, and repeated requests progressively consume process memory until service availability is lost.
Summary
What happened
Memory leak in DCMTK dcmqrdb 3.6.6 and earlier allows remote attackers to exhaust memory and interrupt the service via crafted requests. Error paths in the dcmnet association parser leave heap-allocated presentation-context and user-information list entries unreleased after malformed data is rejected. Network access to a running dcmqrdb service is sufficient, and repeated requests progressively consume process memory until service availability is lost.
The record
- CVE
- CVE-2021-41687
- 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