DCMTK up to 3.6.6 dcmqrdb memory leak

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.4$0-$5k0.00

A vulnerability was found in DCMTK up to 3.6.6. It has been declared as problematic. This vulnerability affects an unknown part of the component dcmqrdb. The manipulation with an unknown input leads to a memory leak vulnerability. The CWE definition for the vulnerability is CWE-401. The software does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. As an impact it is known to affect availability. CVE summarizes:

DCMTK through 3.6.6 does not handle memory free properly. The malloced memory for storing all file information are recorded in a global variable LST and are not freed properly. Sending specific requests to the dcmqrdb program can incur a memory leak. An attacker can use it to launch a DoS attack.

The weakness was disclosed 06/29/2022 as a9697dfeb672b0b9412c00c7d36d801e27ec85cb. The advisory is shared for download at github.com. This vulnerability was named CVE-2021-41690 since 09/27/2021. There are neither technical details nor an exploit publicly available.

Applying the patch a9697dfeb672b0b9412c00c7d36d801e27ec85cb is able to eliminate this problem. The bugfix is ready for download at github.com.

Productinfo

Name

License

  • open-source

CPE 2.3info

CPE 2.2info

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.4

VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

NVD Base Score: 🔒

Exploitinginfo

Class: Memory leak
CWE: CWE-401 / CWE-404
ATT&CK: Unknown

Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-Dayunlockunlockunlockunlock
Todayunlockunlockunlockunlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔒

Patch: a9697dfeb672b0b9412c00c7d36d801e27ec85cb

Timelineinfo

09/27/2021 CVE reserved
06/29/2022 +275 days Advisory disclosed
06/29/2022 +0 days VulDB entry created
07/16/2022 +17 days VulDB last update

Sourcesinfo

Advisory: a9697dfeb672b0b9412c00c7d36d801e27ec85cb
Status: Confirmed

CVE: CVE-2021-41690 (🔒)

Entryinfo

Created: 06/29/2022 08:06 AM
Updated: 07/16/2022 11:43 AM
Changes: 06/29/2022 08:06 AM (41), 07/16/2022 11:43 AM (18)
Complete: 🔍

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!