Automatically applying components based on crash stacktrace and information from OWNERS files.
If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Richard and Dan, can you please take a look?
dbfuzz2 test case attached. Stack trace below.
Removed security labels because dbfuzz2 targets database corruption handling, and its test cases can only be turned into attacks with local disk access, which is outside of Chrome's threat model.
==2269625==ERROR: AddressSanitizer: SEGV on unknown address 0xbebe0004 (pc 0xf7d3b927 bp 0xffd76c28 sp 0xffd76ba0 T0)
==2269625==The signal is caused by a READ memory access.
SCARINESS: 20 (wild-addr-read)
#0 0xf7d3b926 in vdbeCompareMemString third_party/sqlite/amalgamation/sqlite3.c
#1 0xf7d41e68 in sqlite3VdbeRecordCompareWithSkip third_party/sqlite/amalgamation/sqlite3.c:80187:16
#2 0xf7d40a28 in vdbeRecordCompareInt third_party/sqlite/amalgamation/sqlite3.c:80356:11
#3 0xf7d2b40f in sqlite3BtreeMovetoUnpacked third_party/sqlite/amalgamation/sqlite3.c
#4 0xf7d3cf23 in btreeMoveto third_party/sqlite/amalgamation/sqlite3.c:63834:8
#5 0xf7d3cb9a in btreeRestoreCursorPosition third_party/sqlite/amalgamation/sqlite3.c:63858:8
#6 0xf7d432a3 in btreeNext third_party/sqlite/amalgamation/sqlite3.c:68628:10
#7 0xf7d07f07 in sqlite3VdbeExec third_party/sqlite/amalgamation/sqlite3.c:88333:8
#8 0xf7c97b5f in sqlite3Step third_party/sqlite/amalgamation/sqlite3.c:81445:10
#9 0xf7c8c36c in sqlite3_step third_party/sqlite/amalgamation/sqlite3.c:81508:16
#10 0xf7ca2bf7 in sqlite3_exec third_party/sqlite/amalgamation/sqlite3.c:118093:12
#11 0x566f40ae in LLVMFuzzerTestOneInput third_party/sqlite/src/test/dbfuzz2.c:95:5
ClusterFuzz testcase 6329377709228032 is verified as fixed, so closing issue as verified.
If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Comment 1 by ClusterFuzz
, Yesterday (36 hours ago)Labels: Test-Predator-Auto-Components