Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically adding ccs based on OWNERS file / target commit history.

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

Marking type=BUG as dbfuzz2 is a stability fuzzer.

Issue has a component, but no priority. Updating to have default priority (Pri-2)

ClusterFuzz has detected this issue as fixed in range 622587:622639.

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

Fuzzer: libFuzzer_sqlite3_dbfuzz2_fuzzer
Fuzz target binary: sqlite3_dbfuzz2_fuzzer
Job Type: chromeos_libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Heap-buffer-overflow READ 1
Crash Address: 0x6150000c6690
Crash State:
  serialGet
  sqlite3VdbeSerialGet
  sqlite3VdbeRecordUnpack
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Fixed: https://clusterfuzz.com/revisions?job=chromeos_libfuzzer_chrome_asan&range=622587:622639

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

See https://github.com/google/clusterfuzz-tools 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.

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

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