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

Issue 907693 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

CHECK failure: buffer != nullptr in decode_buffer.h

Project Member Reported by ClusterFuzz, Nov 22

Issue description

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

Fuzzer: libFuzzer_net_hpack_decoder_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  buffer != nullptr in decode_buffer.h
  http2::DecodeBuffer::DecodeBuffer
  hpack_decoder_fuzzer.cc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=610235:610237

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

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 22

Components: Internals>Network>HTTP2
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 22

Cc: pmeenan@chromium.org
Labels: ClusterFuzz-Auto-CC
Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.
Project Member

Comment 3 by ClusterFuzz, Nov 22

Labels: Test-Predator-Auto-Owner
Owner: mmoroz@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/c416f80a900acf43478a6ad469ed0fa4af2e35aa (Refactor base::FuzzedDataProvider and fix the calling sites. The main goals:).

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

Comment 4 by bugdroid1@chromium.org, Nov 27

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

commit c76a024376c9f8d6a5053bb0b6820bfeb55c861a
Author: Max Moroz <mmoroz@chromium.org>
Date: Tue Nov 27 02:52:21 2018

[net] Fix hpack_decoder_fuzzer not to pass nullptr to http2::DecodeBuffer constructor.

Bug:  907693 
Change-Id: I3514c9aa5aacf68e7b9964b637ac79c5fbe29b50
Reviewed-on: https://chromium-review.googlesource.com/c/1351286
Reviewed-by: Ryan Hamilton <rch@chromium.org>
Commit-Queue: Max Moroz <mmoroz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611004}
[modify] https://crrev.com/c76a024376c9f8d6a5053bb0b6820bfeb55c861a/net/third_party/http2/hpack/decoder/hpack_decoder_fuzzer.cc

Project Member

Comment 5 by ClusterFuzz, Nov 27

ClusterFuzz has detected this issue as fixed in range 611003:611007.

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

Fuzzer: libFuzzer_net_hpack_decoder_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  buffer != nullptr in decode_buffer.h
  http2::DecodeBuffer::DecodeBuffer
  hpack_decoder_fuzzer.cc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=610235:610237
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=611003:611007

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

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 6 by ClusterFuzz, Nov 27

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