CVE-2019-20009 json
An issue was discovered in GNU LibreDWG before 0.93.
published 2019-12-27 6 y ago modified 2026-06-17 4 mo ago also EUVD-2019-10565
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 72%
- public exploits
- 0
- none known
Summary
An issue was discovered in GNU LibreDWG before 0.93. Crafted input will lead to an attempted excessive memory allocation in dwg_decode_SPLINE_private in dwg.spec.
Patch / fix
- gnu libredwg 0.9.3
- 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
Exploit prediction
1.37% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/LibreDWG/libredwg/issues/176 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/LibreDWG/libredwg/issues/176#issue-541977765 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
-
github.com
/LibreDWG/libredwg/compare/0.9.2...0.9.3
patch, third-party-advisory
-
github.com
/LibreDWG/libredwg/issues/176
exploit, issue-tracking, third-party-advisory
-
github.com
/LibreDWG/libredwg/issues/176#issue-541977765
exploit, issue-tracking, third-party-advisory
-
lists.opensuse.org
/opensuse-security-announce/2020-01/msg00033.html
vendor-advisory, mailing-list, third-party-advisory
-
lists.opensuse.org
/opensuse-security-announce/2020-01/msg00045.html
vendor-advisory, mailing-list, third-party-advisory
Sources
- CVE List CVE-2019-20009
- NVD CVE-2019-20009
Fencer Vulns 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.