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

Issue 660680 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Crash in base::debug::DebugBreak

Project Member Reported by ClusterFuzz, Oct 29 2016

Issue description

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5557756334702592

Fuzzer: libfuzzer_net_http_proxy_client_socket_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x03e9000041fc
Crash State:
  base::debug::DebugBreak
  net::HttpAuthController::ResetAuth
  _start
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=395717:395804

Minimized Testcase (0.23 Kb):
Download: https://cluster-fuzz.appspot.com/download/AMIfv96ejVD61aXSBrL2fFwHcCAY9J971SQp7yX7C7bkw0bAZJETuB7sFs2NwoKsfq1sOCZ8UFxm8YEjQTMrfhQGeFMtl3_f0HPDlI-GzoKHqGjxddXkbvjMQoZBAjL4KCnDpOY9p6zZekcs9eMGoK7Qqd0PUtE4-w?testcase_id=5557756334702592
HTTP/5.0 407
Proxy-�uthentihatHTTP 407
Proxy-Authenticate:Digest nonce=0C(Basic
Content-Length:00

 HTHTTP 407
Proxy-Authenticate:Digest stale=true,"H*HTTP/407
Proxy-Authenticate:Digest noNce=��!0die:K/g

 401*HTTP/ 407
Conteit-LeN


Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
 
Owner: mmenke@chromium.org
Status: Assigned (was: Untriaged)
mmenke @ could you please look into this.please feel free to re-assigned back if needed. thanks in advance !

Comment 2 by mmenke@chromium.org, Oct 31 2016

Cc: mmenke@chromium.org
Owner: mmohammad@chromium.org
I can't reproduce this locally, on a fresh checkout - that input seems to run fine.  args.gn contains the following:

is_debug = true
use_libfuzzer = true
is_asan = true
enable_nacl = false
proprietary_codecs = true
ffmpeg_branding = "ChromeOS"
use_goma = true

Running with:  ./out/afl/net_http_proxy_client_socket_fuzzer ../fuzz-3-net_http_proxy_client_socket_fuzzer -runs=1000

Tried just 1 run as well.  Am I missing something?  If not, I think I'm going to need more to go one.  The report claims it's a debug build, so maybe a symbolized call stack?

Comment 3 by mmenke@chromium.org, Oct 31 2016

Cc: -mmenke@chromium.org mmohammad@chromium.org
Owner: mmenke@chromium.org
Nevermind, turned out I had a local change that broke it (Thought I reverted relevant changes, but had more than I thought)

Comment 4 by mmenke@chromium.org, Oct 31 2016

Cc: mmenke@chromium.org
Owner: asanka@chromium.org
[asanka]:  Mind taking this?  I don't understand the DCHECK that's failing (the "DCHECK(identity_.invalid || credentials.Empty())" in "HttpAuthController::ResetAuth()")
Project Member

Comment 5 by ClusterFuzz, Nov 22 2016

ClusterFuzz has detected this issue as fixed in range 433648:433747.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5557756334702592

Fuzzer: libfuzzer_net_http_proxy_client_socket_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x03e9000041fc
Crash State:
  base::debug::DebugBreak
  net::HttpAuthController::ResetAuth
  _start
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=395717:395804
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=433648:433747

Minimized Testcase (0.23 Kb):
Download: https://cluster-fuzz.appspot.com/download/AMIfv96ejVD61aXSBrL2fFwHcCAY9J971SQp7yX7C7bkw0bAZJETuB7sFs2NwoKsfq1sOCZ8UFxm8YEjQTMrfhQGeFMtl3_f0HPDlI-GzoKHqGjxddXkbvjMQoZBAjL4KCnDpOY9p6zZekcs9eMGoK7Qqd0PUtE4-w?testcase_id=5557756334702592
HTTP/5.0 407
Proxy-�uthentihatHTTP 407
Proxy-Authenticate:Digest nonce=0C(Basic
Content-Length:00

 HTHTTP 407
Proxy-Authenticate:Digest stale=true,"H*HTTP/407
Proxy-Authenticate:Digest noNce=��!0die:K/g

 401*HTTP/ 407
Conteit-LeN


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

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

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

Comment 7 by sheriffbot@chromium.org, Nov 22 2016

Labels: -Restrict-View-EditIssue
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