CVE-2019-20201
- EPSS 0.41%
- Published 31.12.2019 21:15:12
- Last modified 21.11.2024 04:38:11
An issue was discovered in ezXML 0.8.3 through 0.8.6. The ezxml_parse_* functions mishandle XML entities, leading to an infinite loop in which memory allocations occur.
CVE-2019-20200
- EPSS 0.52%
- Published 31.12.2019 21:15:11
- Last modified 21.11.2024 04:38:11
An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_decode, while parsing crafted a XML file, performs incorrect memory handling, leading to a heap-based buffer over-read in the "normalize line endings" feature.
CVE-2019-20199
- EPSS 0.79%
- Published 31.12.2019 21:15:11
- Last modified 21.11.2024 04:38:11
An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_decode, while parsing a crafted XML file, performs incorrect memory handling, leading to NULL pointer dereference while running strlen() on a NULL pointer.
CVE-2019-20198
- EPSS 0.73%
- Published 31.12.2019 21:15:11
- Last modified 21.11.2024 04:38:11
An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_ent_ok() mishandles recursion, leading to stack consumption for a crafted XML file.
CVE-2019-20005
- EPSS 0.68%
- Published 26.12.2019 22:15:10
- Last modified 21.11.2024 04:37:52
An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_decode, while parsing a crafted XML file, performs incorrect memory handling, leading to a heap-based buffer over-read while running strchr() starting with a pointer after a '\0...
CVE-2019-20007
- EPSS 0.85%
- Published 26.12.2019 22:15:10
- Last modified 21.11.2024 04:37:52
An issue was discovered in ezXML 0.8.2 through 0.8.6. The function ezxml_str2utf8, while parsing a crafted XML file, performs zero-length reallocation in ezxml.c, leading to returning a NULL pointer (in some compilers). After this, the function ezxml...
CVE-2019-20006
- EPSS 0.44%
- Published 26.12.2019 22:15:10
- Last modified 21.11.2024 04:37:52
An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_char_content puts a pointer to the internal address of a larger block as xml->txt. This is later deallocated (using free), leading to a segmentation fault.