New issue
Advanced search Search tips

Issue 716532 link

Starred by 1 user

Issue metadata

Status: Verified
Owner: ----
Closed: May 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug



Sign in to add a comment

Stack-overflow in xmlParseConditionalSections

Project Member Reported by ClusterFuzz, Apr 28 2017

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=6240969092759552

Fuzzer: libfuzzer_libxml_xml_read_memory_fuzzer
Job Type: mac_libfuzzer_chrome_asan
Platform Id: mac

Crash Type: Stack-overflow
Crash Address: 0x7fff58e3fff8
Crash State:
  xmlParseConditionalSections
  
Sanitizer: address (ASAN)

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6240969092759552


Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
 

Comment 1 by shrike@chromium.org, Apr 28 2017

Components: Blink>XML
Project Member

Comment 2 by ClusterFuzz, May 27 2017

ClusterFuzz has detected this issue as fixed in range 474926:474952.

Detailed report: https://clusterfuzz.com/testcase?key=6240969092759552

Fuzzer: libfuzzer_libxml_xml_read_memory_fuzzer
Job Type: mac_libfuzzer_chrome_asan
Platform Id: mac

Crash Type: Stack-overflow
Crash Address: 0x7fff58e3fff8
Crash State:
  xmlParseConditionalSections
  
Sanitizer: address (ASAN)

Fixed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=474926:474952

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6240969092759552


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.
Project Member

Comment 3 by ClusterFuzz, May 27 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Untriaged)
ClusterFuzz testcase 6240969092759552 is verified as fixed, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

Sign in to add a comment