New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 768151 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Stack-overflow in xmlParseElement

Project Member Reported by ClusterFuzz, Sep 23 2017

Issue description

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

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.
 
Cc: msrchandra@chromium.org kkaluri@chromium.org
Labels: -Pri-1 M-63 Test-Predator-Wrong Pri-2
Owner: dominicc@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL did not provide any possible suspects.
Using Code Search for the file "parser.c",assigning to the concern owner who might be related to your changes.

@dominicc -- Could you please look into the issue, kindly re-assign if this is not related to your changes.

Thank You.
Project Member

Comment 2 by ClusterFuzz, Oct 1 2017

Components: Blink>XML
Labels: Test-Predator-AutoComponents
Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.
Cc: noel@chromium.org
Labels: ClusterFuzz-Ignore
Owner: joelhockey@chromium.org
Status: WontFix (was: Assigned)
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"));

  ...


Cc: dominicc@chromium.org
 Issue 757159  has been merged into this issue.
 Issue 738947  has been merged into this issue.
Project Member

Comment 6 by ClusterFuzz, Oct 11 2017

Labels: OS-Windows

Comment 7 by mmoroz@google.com, Oct 11 2017

Cc: mbarbe...@chromium.org
Labels: ClusterFuzz-Wrong
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?
Project Member

Comment 8 by ClusterFuzz, Oct 12 2017

Labels: OS-Mac
Project Member

Comment 9 by ClusterFuzz, 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.
Status: Fixed (was: WontFix)
Labels: -Test-Predator-AutoComponents Test-Predator-Auto-Components

Sign in to add a comment