{"id":"CVE-2021-31347","url":"https://www.cyber-defence.io/tools/cve/CVE-2021-31347","generatedAt":"2026-10-27T22:24:54.648Z","title":"An issue was discovered in libezxml.a in ezXML 0.8.6.","description":"An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_parse_str() performs incorrect memory handling while parsing crafted XML files (writing outside a memory region created by mmap).","published":"2021-04-16T18:15:14.000Z","lastModified":"2026-06-17T03:51:35.000Z","status":"Modified","sourceIdentifier":"cve@mitre.org","cvss":{"version":"3.1","score":6.5,"severity":"MEDIUM","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H"},"cwe":["CWE-91"],"affected":["ezxml project/ezxml","debian/debian linux"],"epss":{"score":0.01106,"percentile":0.65601,"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":"low","text":"Lower severity and a low EPSS score (1.11%). Track it; it rarely justifies an emergency change on its own."},"changes":[],"references":[{"url":"https://lists.debian.org/debian-lts-announce/2021/07/msg00005.html","tags":["Mailing List","Third Party Advisory"],"source":"cve@mitre.org"},{"url":"https://sourceforge.net/p/ezxml/bugs/27/","tags":["Exploit","Issue Tracking","Patch","Third Party Advisory"],"source":"cve@mitre.org"},{"url":"https://lists.debian.org/debian-lts-announce/2021/07/msg00005.html","tags":["Mailing List","Third Party Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://sourceforge.net/p/ezxml/bugs/27/","tags":["Exploit","Issue Tracking","Patch","Third Party Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2021-31347","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."}