Описание
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 processing of a string was finished).
Пакеты
| Пакет | Статус | Версия исправления | Релиз | Тип |
|---|---|---|---|---|
| mapcache | unfixed | package | ||
| scilab | fixed | 2024.1.0+dfsg1-1 | package | |
| netcdf | fixed | 1:4.9.0-1 | package | |
| netcdf | ignored | bullseye | package | |
| netcdf | ignored | buster | package | |
| netcdf | not-affected | stretch | package | |
| netcdf-parallel | fixed | 1:4.9.0-1 | package | |
| netcdf-parallel | ignored | bullseye | package | |
| netcdf-parallel | ignored | buster | package |
Примечания
https://sourceforge.net/p/ezxml/bugs/14/
mapcache only uses ezxml to parse config files which are trusted
EPSS
Связанные уязвимости
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 processing of a string was finished).
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 processing of a string was finished).
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 processing of a string was finished).
Уязвимость функции ezxml_decode библиотеки для синтаксического анализа XML-документов ezXML, позволяющая нарушителю вызвать отказ в обслуживании
EPSS