Security readout for executives and security teams
Plain-English summary
DCMTK through 3.6.6 has a memory handling flaw in dcmqrdb. Certain requests can trigger a double free and crash the program, creating a denial-of-service risk for systems using DCMTK DICOM query/retrieve services.
Executive priority
Treat this as a targeted service availability risk, not confirmed system takeover. Prioritize environments where DICOM query/retrieve availability affects clinical or operational workflows, especially internet- or partner-reachable services.
Technical view
The CVE describes a use-after-free style memory lifetime issue leading to double free in DCMTK dcmqrdb. The public record states specific requests can cause denial of service. CVSS, CWE, and precise affected CPE data are not provided in the bundle.
Likely exposure
Exposure is most likely where DCMTK through 3.6.6 is installed and dcmqrdb is enabled or reachable. Medical imaging, PACS, research, or DICOM workflow environments should check package and source-build usage.
Exploitation context
The sources state denial of service is possible, but provide no evidence of active exploitation. The CVE is not marked KEV in the supplied bundle. Public details are limited to affected component, failure mode, and references.
Researcher notes
The bundle lacks CVSS, CWE, affected CPEs, and detailed fixed-version mapping. Analysis should stay scoped to DCMTK through 3.6.6, dcmqrdb, and DoS until vendor or distribution advisories provide more detail.
Mitigation direction
- Identify DCMTK installations and whether dcmqrdb is enabled.
- Apply vendor or distribution dcmtk security updates where available.
- Review the referenced upstream commit for source-built deployments.
- Check Debian LTS advisories if using Debian-packaged dcmtk.
- Reduce external reachability of dcmqrdb where operationally acceptable.
Validation and detection
- Confirm installed DCMTK version and package source.
- Check whether dcmqrdb is running or exposed on networks.
- Verify security update status against vendor advisories.
- Review service logs for unexplained dcmqrdb crashes.
- Document any source builds needing upstream fix review.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2021-41688 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/DCMTK/dcmtkCVE reference
- https://github.com/DCMTK/dcmtk/commit/a9697dfeb672b0b9412c00c7d36d801e27ec85cbCVE reference
- [debian-lts-announce] 20240628 [SECURITY] [DLA 3847-1] dcmtk security updateCVE reference · mailing-list
- https://lists.debian.org/debian-lts-announce/2025/01/msg00032.htmlCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
