New issue
Advanced search Search tips

Issue 919172 link

Starred by 1 user

Issue metadata

Status: Verified
Owner: ----
Closed: Jan 8
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Direct-leak in _ppdOpen

Project Member Reported by ClusterFuzz, Jan 4

Issue description

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

Project: chromeos
Fuzzer: libFuzzer_chromeos_cups_ppdopen_fuzzer
Fuzz target binary: cups_ppdopen_fuzzer
Job Type: libfuzzer_asan_chromeos
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  _ppdOpen
  cups_ppdopen_fuzzer.cc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_asan_chromeos&range=3186655:3189552

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

Issue filed automatically.

See https://chromium.googlesource.com/chromiumos/docs/+/master/fuzzing.md#Reproducing-crashes-from-ClusterFuzz for instructions to reproduce this bug locally.
 
Project Member

Comment 1 by ClusterFuzz, Jan 4

Cc: pawliczek@chromium.org valleau@chromium.org luum@chromium.org skau@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 2 by ClusterFuzz, Jan 8

ClusterFuzz has detected this issue as fixed in range 3325986:3326712.

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

Project: chromeos
Fuzzer: libFuzzer_chromeos_cups_ppdopen_fuzzer
Fuzz target binary: cups_ppdopen_fuzzer
Job Type: libfuzzer_asan_chromeos
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  _ppdOpen
  cups_ppdopen_fuzzer.cc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_asan_chromeos&range=3186655:3189552
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_asan_chromeos&range=3325986:3326712

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

See https://chromium.googlesource.com/chromiumos/docs/+/master/fuzzing.md#Reproducing-crashes-from-ClusterFuzz for instructions to reproduce this bug locally.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

Comment 3 by ClusterFuzz, Jan 8

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