The Manticore function modeling API can be used to override a certain function in the target program with a custom implementation in Python. This can greatly increase performance.
Manticore comes with implementations of function models for some common library routines (core models), and also offers a user API for defining user-defined models.
To use a core model, use the
invoke_model() API. The
available core models are documented in the API Reference:
from manticore.native.models import strcmp addr_of_strcmp = 0x400510 @m.hook(addr_of_strcmp) def strcmp_model(state): state.invoke_model(strcmp)
To implement a user-defined model, implement your model as a Python function, and pass it to
invoke_model(). See the
invoke_model() documentation for more. The
are also good examples to look at and use the same external user API.
Manticore allows you to execute programs with symbolic input, which represents a range of possible inputs. You can do this in a variety of manners.
Throughout these various interfaces, the ‘+’ character is defined to designate a byte of input as symbolic. This allows the user to make input that mixes symbolic and concrete bytes (e.g. known file magic bytes).
To provide a symbolic argument or environment variable on the command line, use the wildcard byte where arguments and environment are specified.:
$ manticore ./binary +++++ +++++ $ manticore ./binary --env VAR1=+++++ --env VAR2=++++++
For API use, use the
envp arguments to the
Manticore.linux('./binary', ['++++++', '++++++'], dict(VAR1='+++++', VAR2='++++++'))
Manticore by default is configured with 256 bytes of symbolic stdin data which is configurable
stdin_size kwarg of
manticore.native.Manticore.linux() , after an optional
concrete data prefix, which can be provided with the
concrete_start kwarg of
Symbolic file input
To provide symbolic input from a file, first create the files that will be opened by the analyzed program, and fill them with wildcard bytes where you would like symbolic data to be.
For command line use, invoke Manticore with the
$ manticore ./binary --file my_symbolic_file1.txt --file my_symbolic_file2.txt
For API use, use the
add_symbolic_file() interface to customize the initial
execution state from an
@m.init def init(initial_state): initial_state.platform.add_symbolic_file('my_symbolic_file1.txt')
Manticore’s socket support is experimental! Sockets are configured to contain 64 bytes of symbolic input.