Issue metadata
Sign in to add a comment
|
Heap-use-after-free in fxcrt::UnownedPtr<CFX_XMLNode>::ProbeForLowSeverityLifetimeIssue |
||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5711884578455552 Fuzzer: libFuzzer_pdfium_xfa_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Heap-use-after-free READ 1 Crash Address: 0x607000010160 Crash State: fxcrt::UnownedPtr<CFX_XMLNode>::ProbeForLowSeverityLifetimeIssue fxcrt::UnownedPtr<CFX_XMLNode>::operator= fxcrt::MaybeOwned<CFX_XMLNode, std::__1::default_delete<CFX_XMLNode> >::Reset Sanitizer: address (ASAN) Recommended Security Severity: High Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=537116:537122 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5711884578455552 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Jun 26 2018
Automatically assigning owner based on suspected regression changelist https://pdfium.googlesource.com/pdfium/+/e40678ed8a22ecd57421877af39cf7f281f618c4 (Make the CFX_XMLNode a MaybeOwned pointer). If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
,
Jun 26 2018
,
Jun 26 2018
Dropping severity, removing security impact. This happens in the *SAN builds and informs us of incorrect pointer ownership.
,
Jun 29 2018
ClusterFuzz has detected this issue as fixed in range 555504:555559. Detailed report: https://clusterfuzz.com/testcase?key=5711884578455552 Fuzzer: libFuzzer_pdfium_xfa_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Heap-use-after-free READ 1 Crash Address: 0x607000010160 Crash State: fxcrt::UnownedPtr<CFX_XMLNode>::ProbeForLowSeverityLifetimeIssue fxcrt::UnownedPtr<CFX_XMLNode>::operator= fxcrt::MaybeOwned<CFX_XMLNode, std::__1::default_delete<CFX_XMLNode> >::Reset Sanitizer: address (ASAN) Recommended Security Severity: High Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=537116:537122 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=555504:555559 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5711884578455552 See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Jun 29 2018
ClusterFuzz testcase 5711884578455552 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Jun 30 2018
,
Oct 6
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ClusterFuzz
, Jun 26 2018Labels: Test-Predator-Auto-Components