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

Issue 689327 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Jun 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Indirect-leak in xmlNewDocElementContent

Project Member Reported by ClusterFuzz, Feb 7 2017

Issue description

Cc: nyerramilli@chromium.org
Labels: Test-Predator-Wrong-CLs M-58
Owner: scottmg@chromium.org
Status: Assigned (was: Untriaged)
Findit cannot find any culprit results.

assigning to /src/third_party/libxml/OWNERS, requesting to check the issue and help.
Cc: dominicc@chromium.org
Project Member

Comment 3 by ClusterFuzz, Jun 21 2017

ClusterFuzz has detected this issue as fixed in range 480710:480765.

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

Fuzzer: libFuzzer_libxml_xml_read_memory_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Indirect-leak
Crash Address: 
Crash State:
  xmlNewDocElementContent
  xmlParseElementMixedContentDecl
  xmlParseElementContentDecl
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=414961:414962
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=480710:480765

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


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 4 by ClusterFuzz, Jun 21 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 5471909975425024 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