Crash in rtc::FifoBuffer::Write |
||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5504980100579328 Fuzzer: afl_pseudotcp_parser_fuzzer Job Type: afl_chrome_asan Platform Id: linux Crash Type: UNKNOWN READ Crash Address: 0x000000000000 Crash State: rtc::FifoBuffer::Write cricket::PseudoTcp::queue cricket::PseudoTcp::queueConnectMessage Regressed: https://cluster-fuzz.appspot.com/revisions?job=afl_chrome_asan&range=419151:419192 Minimized Testcase (0.04 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97ds_Jok39uBoQvR3mJDjf4s2M8GwCHAiN0GRjmS8F_A19zQn5VmaY7f_hTjvAKHxbqEAApob91A-Y03DXNyZsq0241N4E7ouvOkIygXnv8aLXJdiB1iSs6z1vUpjAB1wxX3hR4by85DZjGnmZ5nOGqup-epQ?testcase_id=5504980100579328 Issue manually filed by: mummareddy See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Sep 19 2016
Fuzzer runs PseudoTcp without rtc::Thread initialized. This is not expected to work.
,
Oct 18 2016
,
Nov 22 2016
Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||
►
Sign in to add a comment |
||||
Comment 1 by mummare...@chromium.org
, Sep 16 2016Labels: Te-Logged
Owner: sergeyu@chromium.org
Status: Assigned (was: Untriaged)