Stack-overflow in xmlParseElement |
||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6025693933862912 Fuzzer: libFuzzer_libxml_xml_read_memory_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffc86d11f48 Crash State: xmlParseElement xmlParseContent Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=450672:450717 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6025693933862912 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Oct 1 2017
Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.
,
Oct 11 2017
Test causes stack overflow with a large nested xml input. Locally, I could reproduce this error. However when I increase stack size to around 16MB using setrlimit(), this test runs fine.
Closing, wont fix. Pathalogical input exceeds process stack limit. This is not a security problem.
code:
extern "C" int LLVMFuzzerTestOneInput(const uint8_t* data, size_t size) {
struct rlimit rl = {16*1024*1024, 16*1024*1024};
if (setrlimit(RLIMIT_STACK, &rl) == -1)
exit(printf("failed\n"));
...
,
Oct 11 2017
,
Oct 11 2017
Issue 738947 has been merged into this issue.
,
Oct 11 2017
,
Oct 11 2017
Marty, here is an interesting case with labels assignment. CF has just added "OS-Windows" to this crash, but we neither run this fuzzer on windows nor have similar crashes found on Windows. I suspect that has happened because one of the issues merged above (c#4 and c#5) is a stack overflow crash without stacktrace: https://clusterfuzz.com/v2/testcase-detail/5153707431034880?noredirect=1 As per crash stats, CF believes that it sees the same crash happening on Windows. Should we fix that?
,
Oct 12 2017
,
Oct 17 2017
ClusterFuzz has detected this issue as fixed in range 509033:509059. Detailed report: https://clusterfuzz.com/testcase?key=6025693933862912 Fuzzer: libFuzzer_libxml_xml_read_memory_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffc86d11f48 Crash State: xmlParseElement xmlParseContent Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=450672:450717 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=509033:509059 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6025693933862912 See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Oct 17 2017
,
Nov 7 2017
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by kkaluri@chromium.org
, Sep 25 2017Labels: -Pri-1 M-63 Test-Predator-Wrong Pri-2
Owner: dominicc@chromium.org
Status: Assigned (was: Untriaged)