Running this fuzzer (with either AFL or libFuzzer) writes files to the directory it is being executed in like:

1. ?;-b( ;SEL(SELECT lower( 15000.)-10-1-2 -1-ECT ?@2  =1=*$es+@2_?&#ar* ''*'RELEAE'+#unorSA;EPOINTs2)pt_m(oeere c01-2+1-hange(1026-00:d)S_EsLECT case intsitive_ lower(?NAALYZE  fo1)MAT880)SDORRE;AVEP?OI'TDET;TCSAACOUTe:R?*-a-&)D0!52?el?cCK)treign_key_listEs

2. ??SELET

3. :memory:memory??SELET

This probably makes the fuzzer slower than it needs to be, but it could do worse things like filling up the disk.

Sqlite has a can be built in a fuzzer mode that prevents this and other bad things (like executing shell commands) from happening. 
 

Running this fuzzer (with either AFL or libFuzzer) writes files to the directory it is being executed in like:

1. ?;-b( ;SEL(SELECT lower( 15000.)-10-1-2 -1-ECT ?@2  =1=*$es+@2_?&#ar* ''*'RELEAE'+#unorSA;EPOINTs2)pt_m(oeere c01-2+1-hange(1026-00:d)S_EsLECT case intsitive_ lower(?NAALYZE  fo1)MAT880)SDORRE;AVEP?OI'TDET;TCSAACOUTe:R?*-a-&)D0!52?el?cCK)treign_key_listEs

2. ??SELET

3. :memory:memory??SELET

This probably makes the fuzzer slower than it needs to be, but it could do worse things like filling up the disk.

Sqlite can be built in a fuzzer mode that prevents this and other bad things (like executing shell commands) from happening. I will see if we are/can use it.