{"id":"CVE-2019-20913","url":"https://www.cyber-defence.io/tools/cve/CVE-2019-20913","generatedAt":"2026-10-27T21:14:33.531Z","title":"An issue was discovered in GNU LibreDWG through 0.9.3.","description":"An issue was discovered in GNU LibreDWG through 0.9.3. Crafted input will lead to a heap-based buffer over-read in dwg_encode_entity in common_entity_data.spec.","published":"2020-07-16T18:15:14.000Z","lastModified":"2026-06-17T02:31:26.000Z","status":"Modified","sourceIdentifier":"cve@mitre.org","cvss":{"version":"3.1","score":8.1,"severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H"},"cwe":["CWE-125"],"affected":["gnu/libredwg"],"epss":{"score":0.01245,"percentile":0.691,"date":"2026-10-26","history":[]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"high","text":"High impact if exploited, but EPSS currently rates exploitation as unlikely (1.24%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit."},"changes":[],"references":[{"url":"https://github.com/LibreDWG/libredwg/commit/3f503dd294efc63a59608d8a16058c41d44ba13a","tags":["Patch","Third Party Advisory"],"source":"cve@mitre.org"},{"url":"https://github.com/LibreDWG/libredwg/issues/178","tags":["Exploit","Third Party Advisory"],"source":"cve@mitre.org"},{"url":"https://github.com/LibreDWG/libredwg/commit/3f503dd294efc63a59608d8a16058c41d44ba13a","tags":["Patch","Third Party Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://github.com/LibreDWG/libredwg/issues/178","tags":["Exploit","Third Party Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2019-20913","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}