rpm package
suse/netcdf_4_6_1-gnu-mvapich2-hpc&distro=SUSE Linux Enterprise High Performance Computing 15-ESPOS
pkg:rpm/suse/netcdf_4_6_1-gnu-mvapich2-hpc&distro=SUSE%20Linux%20Enterprise%20High%20Performance%20Computing%2015-ESPOS
Vulnerabilities (16)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2021-31598 | Hig | 7.5 | < 4.6.1-5.7.1 | 4.6.1-5.7.1 | Apr 24, 2021 | An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_decode() performs incorrect memory handling while parsing crafted XML files, leading to a heap-based buffer overflow. | |
| CVE-2021-31348 | Med | 6.5 | < 4.6.1-5.7.1 | 4.6.1-5.7.1 | Apr 16, 2021 | 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 (out-of-bounds read after a certain strcspn failure). | |
| CVE-2021-31347 | Med | 6.5 | < 4.6.1-5.7.1 | 4.6.1-5.7.1 | Apr 16, 2021 | 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). | |
| CVE-2021-31229 | Med | 6.5 | < 4.6.1-5.7.1 | 4.6.1-5.7.1 | Apr 15, 2021 | An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_internal_dtd() performs incorrect memory handling while parsing crafted XML files, which leads to an out-of-bounds write of a one byte constant. | |
| CVE-2021-30485 | Med | 6.5 | < 4.6.1-5.7.1 | 4.6.1-5.7.1 | Apr 11, 2021 | An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_internal_dtd(), while parsing a crafted XML file, performs incorrect memory handling, leading to a NULL pointer dereference while running strcmp() on a NULL pointer. | |
| CVE-2021-26222 | Hig | 8.1 | < 4.6.1-5.7.1 | 4.6.1-5.7.1 | Feb 8, 2021 | The ezxml_new function in ezXML 0.8.6 and earlier is vulnerable to OOB write when opening XML file after exhausting the memory pool. | |
| CVE-2021-26221 | Hig | 8.1 | < 4.6.1-5.7.1 | 4.6.1-5.7.1 | Feb 8, 2021 | The ezxml_new function in ezXML 0.8.6 and earlier is vulnerable to OOB write when opening XML file after exhausting the memory pool. | |
| CVE-2021-26220 | Hig | 8.1 | < 4.6.1-5.7.1 | 4.6.1-5.7.1 | Feb 8, 2021 | The ezxml_toxml function in ezxml 0.8.6 and earlier is vulnerable to OOB write when opening XML file after exhausting the memory pool. | |
| CVE-2019-20202 | Med | 6.5 | < 4.6.1-5.7.1 | 4.6.1-5.7.1 | Dec 31, 2019 | An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_char_content() tries to use realloc on a block that was not allocated, leading to an invalid free and segmentation fault. | |
| CVE-2019-20201 | Med | 6.5 | < 4.6.1-5.7.1 | 4.6.1-5.7.1 | Dec 31, 2019 | 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 | Med | 6.5 | < 4.6.1-5.7.1 | 4.6.1-5.7.1 | Dec 31, 2019 | 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 | Med | 6.5 | < 4.6.1-5.7.1 | 4.6.1-5.7.1 | Dec 31, 2019 | 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 | Med | 6.5 | < 4.6.1-5.7.1 | 4.6.1-5.7.1 | Dec 31, 2019 | 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-20007 | Med | 6.5 | < 4.6.1-5.7.1 | 4.6.1-5.7.1 | Dec 26, 2019 | 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_parse_str does not check whet | |
| CVE-2019-20006 | Hig | 7.5 | < 4.6.1-5.7.1 | 4.6.1-5.7.1 | Dec 26, 2019 | 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. | |
| CVE-2019-20005 | Med | 6.5 | < 4.6.1-5.7.1 | 4.6.1-5.7.1 | Dec 26, 2019 | 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' character (where the process |
- affected < 4.6.1-5.7.1fixed 4.6.1-5.7.1
An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_decode() performs incorrect memory handling while parsing crafted XML files, leading to a heap-based buffer overflow.
- affected < 4.6.1-5.7.1fixed 4.6.1-5.7.1
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 (out-of-bounds read after a certain strcspn failure).
- affected < 4.6.1-5.7.1fixed 4.6.1-5.7.1
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).
- affected < 4.6.1-5.7.1fixed 4.6.1-5.7.1
An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_internal_dtd() performs incorrect memory handling while parsing crafted XML files, which leads to an out-of-bounds write of a one byte constant.
- affected < 4.6.1-5.7.1fixed 4.6.1-5.7.1
An issue was discovered in libezxml.a in ezXML 0.8.6. The function ezxml_internal_dtd(), while parsing a crafted XML file, performs incorrect memory handling, leading to a NULL pointer dereference while running strcmp() on a NULL pointer.
- affected < 4.6.1-5.7.1fixed 4.6.1-5.7.1
The ezxml_new function in ezXML 0.8.6 and earlier is vulnerable to OOB write when opening XML file after exhausting the memory pool.
- affected < 4.6.1-5.7.1fixed 4.6.1-5.7.1
The ezxml_new function in ezXML 0.8.6 and earlier is vulnerable to OOB write when opening XML file after exhausting the memory pool.
- affected < 4.6.1-5.7.1fixed 4.6.1-5.7.1
The ezxml_toxml function in ezxml 0.8.6 and earlier is vulnerable to OOB write when opening XML file after exhausting the memory pool.
- affected < 4.6.1-5.7.1fixed 4.6.1-5.7.1
An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_char_content() tries to use realloc on a block that was not allocated, leading to an invalid free and segmentation fault.
- affected < 4.6.1-5.7.1fixed 4.6.1-5.7.1
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.
- affected < 4.6.1-5.7.1fixed 4.6.1-5.7.1
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.
- affected < 4.6.1-5.7.1fixed 4.6.1-5.7.1
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.
- affected < 4.6.1-5.7.1fixed 4.6.1-5.7.1
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.
- affected < 4.6.1-5.7.1fixed 4.6.1-5.7.1
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_parse_str does not check whet
- affected < 4.6.1-5.7.1fixed 4.6.1-5.7.1
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.
- affected < 4.6.1-5.7.1fixed 4.6.1-5.7.1
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' character (where the process