New issue
Advanced search Search tips

Issue 784145 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

CHECK failure: false. QUIC should always have certificates in quic_chromium_client_session.cc

Project Member Reported by ClusterFuzz, Nov 12 2017

Issue description

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

Fuzzer: libFuzzer_net_quic_stream_factory_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  false. QUIC should always have certificates in quic_chromium_client_session.cc
  net::QuicChromiumClientSession::CanPool
  net::QuicChromiumClientSession::IsAuthorized
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=514627:514664

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Nov 12 2017

Components: Internals>Network>QUIC
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 2 by ClusterFuzz, Nov 12 2017

Labels: Test-Predator-Auto-Owner
Owner: nedwilli...@gmail.com
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/3d55bbb391a5a2e7ba3dd5c083f46bfdb950adcb (Add Quic Stream Factory Fuzzer).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

Comment 3 by rch@chromium.org, Nov 12 2017

Owner: rch@chromium.org

Comment 4 by mmoroz@chromium.org, Nov 13 2017

Cc: nedwilli...@gmail.com mmoroz@chromium.org
Project Member

Comment 5 by bugdroid1@chromium.org, Nov 14 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/0a9f0146134281c2e2be635f90bfae1acaaffdc0

commit 0a9f0146134281c2e2be635f90bfae1acaaffdc0
Author: Ryan Hamilton <rch@chromium.org>
Date: Tue Nov 14 01:27:30 2017

Add proof verification details to quic_stream_factory_fuzzer.cc

BUG= 784145 

Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: Id101b85d3ef54d715bd3be526880ee1e835511ef
Reviewed-on: https://chromium-review.googlesource.com/767057
Reviewed-by: Buck Krasic <ckrasic@chromium.org>
Commit-Queue: Ryan Hamilton <rch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516135}
[modify] https://crrev.com/0a9f0146134281c2e2be635f90bfae1acaaffdc0/net/quic/chromium/quic_stream_factory_fuzzer.cc

Project Member

Comment 6 by ClusterFuzz, Nov 14 2017

ClusterFuzz has detected this issue as fixed in range 516120:516144.

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

Fuzzer: libFuzzer_net_quic_stream_factory_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  false. QUIC should always have certificates in quic_chromium_client_session.cc
  net::QuicChromiumClientSession::CanPool
  net::QuicChromiumClientSession::IsAuthorized
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=514627:514664
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=516120:516144

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

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

Comment 7 by ClusterFuzz, Nov 14 2017

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

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

Sign in to add a comment