Chinfuzz
Tezos smart contract fuzzer
Install / Use
/learn @ant4g0nist/ChinfuzzREADME
Chinfuzz
Chinfuzz enables code coverage fuzzing for Tezos smart contracts
Installation
Dependencies
$ brew tap cuber/homebrew-libsecp256k1
$ brew install libsodium libsecp256k1 gmp pkg-config make
Install chinfuzz:
git clone https://github.com/ant4g0nist/chinfuzz
cd chinfuzz
make
Running make will clone and build llvm and install it to ~/llvm-14.0.4 and install chinfuzz
If you already have a compiled version of llvm/clang, you could run:
LLVM_SYS=~/llvm-14.0.4 make
Usage:
Installing chinfuzz also installs chinstrap.
You can initialise a chinfuzz project by running chinfuzz init. This initialises a chinstrap project and creates an extra folder fuzz where we are going to write our fuzzers.
Folder structure:
.
|____originations
| |____1_samplecontract_origination.py
|____contracts
| |____SampleContract.py
|____tests
| |____sampleContractSmartPy.py
| |____samplecontractPytest.py
|____chinstrap-config.yml
|____.chinstrap
|____fuzz
| |____SampleContractFuzzer.py
|____.secret
You can find more details about chinstrap here: https://chinstrap.io/docs/usage
Chinfuzz takes a contract that has invariants and a fuzzer written in Python as input. Invariants are properties taht should always remain true for all inputs. If it can find some way to falsify the invariant, it saves the input that falsified the invariant.
For each invariant, it generates random inputs and call the entrypoint of contract as specified in the fuzzer and checks if the invariant holds true.
Invariants are expressed inside entrypoints that revert(FAILWITH) if falsified. In the following example, we have declared an invariant, sp.if name == "TEZOS":, to find if there is any name that matches that condition. If so, we trigger failwith(crash).
@sp.entry_point
def setName(self, name):
sp.if name == "TEZOS":
sp.failwith("Boom crash!!!")
self.data.name = name
Lets modify our sample contract from
import smartpy as sp
class SampleContract(sp.Contract):
def __init__(self, value, owner):
self.init_type(sp.TRecord(counter=sp.TInt, owner=sp.TAddress))
self.init(counter=value, owner=owner)
@sp.entry_point
def increment(self, value):
sp.verify(sp.sender == self.data.owner, message="Only owner can increment")
self.data.counter += value
@sp.entry_point
def decrement(self, value):
sp.verify(sp.sender == self.data.owner, message="Only owner can decrement")
self.data.counter -= value
sp.add_compilation_target(
"SampleContract",
SampleContract(0, sp.address("tz1a9GCc4UU6d5Z9spyozgKTARngb8DZKbNe")),
)
to
import smartpy as sp
class SampleContract(sp.Contract):
def __init__(self, value, owner, name):
self.init_type(sp.TRecord(counter=sp.TInt, name= sp.TString, owner=sp.TAddress))
self.init(counter=value, owner=owner, name=name)
@sp.entry_point
def increment(self, value):
sp.verify(sp.sender == self.data.owner, message="Only owner can increment")
self.data.counter += value
@sp.entry_point
def setName(self, name):
sp.if name == "TEZOS":
sp.failwith("Boom crash!!!")
self.data.name = name
@sp.entry_point
def decrement(self, value):
sp.verify(sp.sender == self.data.owner, message="Only owner can decrement")
self.data.counter -= value
sp.add_compilation_target(
"SampleContract",
SampleContract(0, sp.address("tz1a9GCc4UU6d5Z9spyozgKTARngb8DZKbNe"), "yolo"),
)
We added one extra endpoint setName that takes a string as parameter.
Now, we compile the contract:
chinstrap compile
Now we have to write our fuzzer. Inside the fuzz, chinfuzz init command should have added a file named SampleContractFuzzer.py with the following content:
from chinfuzz.core import fuzz
from chinstrap.tests import getContractInterface
owner = "tz1YtuZ4vhzzn7ssCt93Put8U9UJDdvCXci4"
def ChinfuzzFuzzerTestOneInput(data):
if len(data)>10:
return
fdp = fuzz.FuzzedDataProvider(data)
data = fdp.ConsumeString(100)
contract = getContractInterface("SampleContract")
storage = {"owner": owner, "counter": 0, "name": "yolo"}
contract.setName(data.encode("ascii", "ignore").decode()).interpret(storage=storage, source=owner)
To start fuzzing, we simply just run:
chinfuzz fuzz -f fuzz/SampleContractFuzzer.py

FuzzedDataProvider:
Often, a bytes object is not convenient input to your code being fuzzed. Similar to libFuzzer, we have a FuzzedDataProvider to translate these bytes into other input forms.
Functions available:
- fuzz.ConsumeUnicode(count)
- fuzz.ConsumeUnicodeNoSurrogates(count)
- fuzz.ConsumeBytes(count)
- fuzz.ConsumeString(count)
- fuzz.ConsumeInt(count)
- fuzz.ConsumeUInt(count)
- fuzz.ConsumeIntInRange(min, max)
- fuzz.ConsumeIntList(count, bytes)
- fuzz.ConsumeIntListInRange(count, min, max)
- fuzz.ConsumeFloat(count)
- fuzz.ConsumeRegularFloat(count)
- fuzz.ConsumeProbability(count)
- fuzz.ConsumeFloatInRange(min, max)
- fuzz.ConsumeFloatList(count)
- fuzz.ConsumeRegularFloatList(count)
- fuzz.ConsumeProbabilityList(count)
- fuzz.ConsumeFloatListInRange(count, min, max)
- fuzz.ConsumeBool(count)
LibFuzzer flags
Usage:
chinfuzz fuzz -f fuzz/SampleContractFuzzer.py -- -runs=1337
LibFuzzer flags available:
- verbosity : 1 Verbosity level.
- seed : 0 Random seed. If 0, seed is generated.
- runs -: 1 Number of individual test runs (-1 for infinite runs).
- max_len : 0 Maximum length of the test input. If 0, libFuzzer tries to guess a good value based on the corpus and reports it.
- len_control 10: 0 Try generating small inputs first, then try larger inputs over time. Specifies the rate at which the length limit is increased (smaller == faster). If 0, immediately try inputs with size up to max_len. Default value is 0, if LLVMFuzzerCustomMutator is used.
- seed_inputs : 0 A comma-separated list of input files to use as an additional seed corpus. Alternatively, an "@" followed by the name of a file containing the comma-separated list.
- keep_seed : 0 If 1, keep seed inputs in the corpus even if they do not produce new coverage. When used with |reduce_inputs==1|, the seed inputs will never be reduced. This option can be useful when seeds arenot properly formed for the fuzz target but still have useful snippets.
- cross_over : 1 If 1, cross over inputs.
- cross_over_uniform_dist : 0 Experimental. If 1, use a uniform probability distribution when choosing inputs to cross over with. Some of the inputs in the corpus may never get chosen for mutation depending on the input mutation scheduling policy. With this flag, all inputs, regardless of the input mutation scheduling policy, can be chosen as an input to cross over with. This can be particularly useful with |keep_seed==1|; all the initial seed inputs, even though they do not increase coverage because they are not properly formed, will still be chosen as an input to cross over with.
- mutate_depth : 5 Apply this number of consecutive mutations to each input.
- reduce_depth : 0 Experimental/internal. Reduce depth if mutations lose unique features
- shuffle : 1 Shuffle inputs at startup
- prefer_small : 1 If 1, always prefer smaller inputs during the corpus shuffle.
- timeout 120: 0 Timeout in seconds (if positive). If one unit runs more than this number of seconds the process will abort.
- error_exitcode 7: 7 When libFuzzer itself reports a bug this exit code will be used.
- timeout_exitcode 7: 0 When libFuzzer reports a timeout this exit code will be used.
- max_total_time : 0 If positive, indicates the maximal total time in seconds to run the fuzzer.
- help : 0 Print help.
- fork : 0 Experimental mode where fuzzing happens in a subprocess
- fork_corpus_groups : 0 For fork mode, enable the corpus-group strategy, The main corpus will be grouped according to size, and each sub-process will randomly select seeds from different groups as the sub-corpus.
- ignore_timeouts : 1 Ignore timeouts in fork mode
- ignore_ooms : 1 Ignore OOMs in fork mode
- ignore_crashes : 0 Ignore crashes in fork mode
- merge : 0 If 1, the 2-nd, 3-rd, etc corpora will be merged into the 1-st corpus. Only interesting units will be taken. This flag can be used to minimize a corpus.
- set_cover_merge : 0 If 1, the 2-nd, 3-rd, etc corpora will be merged into the 1-st corpus. Same as the 'merge' flag, but uses the standard greedy algorithm for the set cover problem to compute an approximation of the minimum set of testcases that provide the same coverage as the initial corpora
- stop_file : 0 Stop fuzzing ASAP if this file exists
- merge_control_file : 0 Specify a control file used for the merge process. If a merge process gets killed it tries to leave this file in a state suitable for resuming the merge. By default a temporary file will be used.The same file can be used for multistep merge process.
- minimize_crash : 0 If 1, minimizes the provided crash input. Use with -runs=N or -max_total_time=N to limit the number attempts. Use with -exact_artifact_path to specif
