Find it and CL did not provide any possible suspect.
Using code search for file "http_proxy_client_socket_fuzzer.cc" from line #31 suspecting the below change
Review URL: https://codereview.chromium.org/2250263003

csharrison@ - Observed some changes on this file so assigning to you, could you please check if this is caused with respect to your change, if not please help us in reassign the issue to the right owner.

Thanks!

Marking as untriaged so an auth person can take a look. Asanka, you're the only one I know who triages this component :) so cc.

I'll have a look, but it will have to be next week when I'm back in the office.

ClusterFuzz has detected this issue as fixed in range 455091:455226.

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

Fuzzer: libfuzzer_net_http_proxy_client_socket_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x03e900001f86
Crash State:
  base::debug::DebugBreak
  net::HttpAuthController::ResetAuth
  _start
  
Sanitizer: address (ASAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=433648:433747
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=455091:455226

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv97YQ8ozovdojkuWp7vqntYzUElP0-1xrKKDQnOk8Gbxe9gV7lrtSyYlGb2XgMOCkOmdwv3rLoM10bHSKkSECjBBAIAARWi80-77OTqbSmIK2KyvzMHhjqKt5npFwl9_EM4VbTC9ZoDOC0FbaJw6MSOTWjG1okFX5G_dgeZIwmh8ICbY_rSdlUPkcoytx2yQqCuOPm0H1vMn4LFE0gehIitK6rsapF4zXtr7MKna7YIkTh5Fp7GfQ5H2p3iGvYAwSq0HoOeAF1Kw4jBKa6AR4KzbT-75utNuvcusTsHGCbHT4hYYlp8wGFS1TygUvU-5DkF2nYUMFJ97UzNla2wpIRx3zLocj7MR9YOjFhi3aNXtNj22rGo?testcase_id=5016379649687552


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.

ClusterFuzz testcase 5016379649687552 is verified as fixed, so closing issue.

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