CVE-2019-9771 json
An issue was discovered in GNU LibreDWG 0.7 and 0.7.1645.
published 7y ago modified 4mo ago also EUVD-2019-19133
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.8%
- EPSS 2.8% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- libredwg openSUSE Tumbleweed 0.11.1-1.6
- libredwg Package Hub 15 SP1 0.9.3-bp151.2.3.1
- libredwg openSUSE Leap 15.1 0.9.3-lp151.2.3.1
opensuse advisories openSUSE-SU-2024:10981-1openSUSE-SU-2020:0095-1openSUSE-SU-2020:0068-1
Is CVE-2019-9771 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
2.77% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- savannah.gnu.org https://savannah.gnu.org/bugs/index.php?55893 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/LibreDWG/libredwg/issues/99 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-476 NULL Pointer Dereference
References
-
savannah.gnu.org
/bugs/index.php?55893
exploit, third-party-advisory
-
github.com
/LibreDWG/libredwg/issues/99
exploit, third-party-advisory
-
lists.opensuse.org
/opensuse-security-announce/2020-01/msg00033.html
vendor-advisory, third-party-advisory
-
lists.opensuse.org
/opensuse-security-announce/2020-01/msg00045.html
vendor-advisory, third-party-advisory
-
securityfocus.com
/bid/107447
vdb-entry, broken-link, third-party-advisory
Sources
- CVE List CVE-2019-9771
- NVD CVE-2019-9771
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.