New issue
Advanced search Search tips

Issue 762852 link

Starred by 2 users

Issue metadata

Status: Verified
Owner: ----
Closed: Sep 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference READ in base::CommandLine::HasSwitch

Project Member Reported by ClusterFuzz, Sep 7 2017

Issue description

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

Fuzzer: libFuzzer_gpu_fuzzer
Job Type: mac_libfuzzer_chrome_asan
Platform Id: mac

Crash Type: Null-dereference READ
Crash Address: 0x000000000038
Crash State:
  base::CommandLine::HasSwitch
  base::SysInfo::AmountOfPhysicalMemory
  base::SysInfo::AmountOfPhysicalMemoryMB
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=499694:499767

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
 
Labels: Test-Predator-Wrong-CLs M-63
Labels: CF-NeedsTriage
Project Member

Comment 3 by ClusterFuzz, Sep 12 2017

ClusterFuzz has detected this issue as fixed in range 500330:501042.

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

Fuzzer: libFuzzer_gpu_fuzzer
Job Type: mac_libfuzzer_chrome_asan
Platform Id: mac

Crash Type: Null-dereference READ
Crash Address: 0x000000000038
Crash State:
  base::CommandLine::HasSwitch
  base::SysInfo::AmountOfPhysicalMemory
  base::SysInfo::AmountOfPhysicalMemoryMB
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=499694:499767
Fixed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=500330:501042

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

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 4 by ClusterFuzz, Sep 12 2017

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