Manalyze
Monthly
Integer underflow in the PE parser of Manalyze 1.0.0 (PE::_parse_debug in manape/pe.cpp) can be triggered when the tool processes a crafted Portable Executable whose IMAGE_DEBUG_MISC debug-directory entry declares a Length smaller than the misc structure header, causing the computed string length to wrap to a very large unsigned value and the parser to read beyond the intended buffer. Exploitation is not remote in practice: it requires a local user (typically a malware analyst) to voluntarily run the unpatched Manalyze CLI against the malicious sample, so the assessed risk is low (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L), with impact largely confined to the parsing process - the tag 'Information Disclosure' reflects the out-of-bounds read potential rather than confirmed data exfiltration. No public exploit code and no active exploitation have been identified at time of analysis, and an upstream fix commit (3e299685759f4f767088871de58c5d07f98ee382) is available.
Integer underflow in the PE parser of Manalyze 1.0.0 (PE::_parse_debug in manape/pe.cpp) can be triggered when the tool processes a crafted Portable Executable whose IMAGE_DEBUG_MISC debug-directory entry declares a Length smaller than the misc structure header, causing the computed string length to wrap to a very large unsigned value and the parser to read beyond the intended buffer. Exploitation is not remote in practice: it requires a local user (typically a malware analyst) to voluntarily run the unpatched Manalyze CLI against the malicious sample, so the assessed risk is low (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L), with impact largely confined to the parsing process - the tag 'Information Disclosure' reflects the out-of-bounds read potential rather than confirmed data exfiltration. No public exploit code and no active exploitation have been identified at time of analysis, and an upstream fix commit (3e299685759f4f767088871de58c5d07f98ee382) is available.