GNU LibreDWG up to 0.92 dwg.spec decode_3dsolid resource consumption

Summaryinfo

A vulnerability, which was classified as problematic, has been found in GNU LibreDWG up to 0.92. Affected by this vulnerability is the function decode_3dsolid of the file dwg.spec. The manipulation leads to resource consumption. This vulnerability is referenced as CVE-2019-20013. Remote exploitation of the attack is possible. No exploit is available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in GNU LibreDWG up to 0.92 (Image Processing Software) and classified as problematic. This issue affects the function decode_3dsolid of the file dwg.spec. The manipulation with an unknown input leads to a resource consumption vulnerability. Using CWE to declare the problem leads to CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. Impacted is availability. The summary by CVE is:

An issue was discovered in GNU LibreDWG before 0.93. Crafted input will lead to an attempted excessive memory allocation in decode_3dsolid in dwg.spec.

The weakness was published 12/27/2019. The identification of this vulnerability is CVE-2019-20013 since 12/27/2019. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.

Upgrading to version 0.93 eliminates this vulnerability.

Similar entries are available at VDB-147787, VDB-147786, VDB-147784 and VDB-147783. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Image Processing Software

Vendor

• GNU

Name

• LibreDWG

Version

• 0.1
• 0.2
• 0.3
• 0.4
• 0.5
• 0.6
• 0.7
• 0.8
• 0.9
• 0.10
• 0.11
• 0.12
• 0.13
• 0.14
• 0.15
• 0.16
• 0.17
• 0.18
• 0.19
• 0.20
• 0.21
• 0.22
• 0.23
• 0.24
• 0.25
• 0.26
• 0.27
• 0.28
• 0.29
• 0.30
• 0.31
• 0.32
• 0.33
• 0.34
• 0.35
• 0.36
• 0.37
• 0.38
• 0.39
• 0.40
• 0.41
• 0.42
• 0.43
• 0.44
• 0.45
• 0.46
• 0.47
• 0.48
• 0.49
• 0.50
• 0.51
• 0.52
• 0.53
• 0.54
• 0.55
• 0.56
• 0.57
• 0.58
• 0.59
• 0.60
• 0.61
• 0.62
• 0.63
• 0.64
• 0.65
• 0.66
• 0.67
• 0.68
• 0.69
• 0.70
• 0.71
• 0.72
• 0.73
• 0.74
• 0.75
• 0.76
• 0.77
• 0.78
• 0.79
• 0.80
• 0.81
• 0.82
• 0.83
• 0.84
• 0.85
• 0.86
• 0.87
• 0.88
• 0.89
• 0.90
• 0.91
• 0.92

License

• open-source

Website

• Vendor: https://www.gnu.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion