GNU LibreDWG 0.7/0.7.1645 bits.c bit_convert_TU null pointer dereference

CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in GNU LibreDWG 0.7/0.7.1645. Affected is the function bit_convert_TU
of the file bits.c. The manipulation leads to null pointer dereference.
This vulnerability is traded as CVE-2019-9771. It is possible to launch the attack remotely. There is no exploit available.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Details
A vulnerability was found in GNU LibreDWG 0.7/0.7.1645 (Image Processing Software). It has been rated as problematic. This issue affects the function bit_convert_TU
of the file bits.c. The manipulation with an unknown input leads to a null pointer dereference vulnerability. Using CWE to declare the problem leads to CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. Impacted is availability. The summary by CVE is:
An issue was discovered in GNU LibreDWG 0.7 and 0.7.1645. There is a NULL pointer dereference in the function bit_convert_TU at bits.c.
The bug was discovered 03/12/2019. The weakness was presented 03/14/2019 (Website). It is possible to read the advisory at securityfocus.com. The identification of this vulnerability is CVE-2019-9771 since 03/14/2019. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 2 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-131730, VDB-131724, VDB-131725 and VDB-131726 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/12/2019 🔍03/14/2019 🔍
03/14/2019 🔍
03/14/2019 🔍
08/01/2023 🔍
Sources
Vendor: gnu.orgAdvisory: 99⛔
Status: Not defined
CVE: CVE-2019-9771 (🔍)
GCVE (CVE): GCVE-0-2019-9771
GCVE (VulDB): GCVE-100-131723
SecurityFocus: 107447
See also: 🔍
Entry
Created: 03/14/2019 02:10 PMUpdated: 08/01/2023 11:20 AM
Changes: 03/14/2019 02:10 PM (56), 05/16/2020 04:14 PM (2), 08/01/2023 11:20 AM (5)
Complete: 🔍
Cache ID: 18:98D:40
No comments yet. Languages: en.
Please log in to comment.