Open 4n0nym4u5 opened 2 months ago
This issue got associated with CVE-2024-50615
Hi,
If the assertion is only triggered in debug mode, what happens when the code is compiled and running in non-debug mode ? Presumably the assertion is not triggered, but does the error condition detected by the assertion in debug mode not cause a different error in non-debug mode ? And what is the impact of that error (crash, malfunction, etc ...) ?
If the crash is avoided in non debug mode, it seems that this could be a mitigation for the CVE, no ?
Description
The latest version of tinyxml2 was discovered to contain a reachable assertion
digit == 0 || mult <= UINT_MAX / digit failed
vulnerability in tinyxml2.cpp:545 tinyxml2::XMLUtil::GetCharacterRef() when parsing a specially crafted XML file. This vulnerability leads to a Denial of Service (DoS).ASAN Log
Proof-of-Concept Files
poc
Reproduction
Results
Environment