perform analysis to find input-state correspondence and then add the constraints in the state

identify the crash location and then generate a coredump before crashing

generate a concrete trace and maybe core dump

create an angr project

dumps a CGC exploit. XXX: just python script for now.

Creates a simple C file to do the type1 exploit :param filename: dumps the code to this path if filename is not None :return:

Creates a simple C file to do the type1 exploit :param filename: dumps the code to this path if filename is not None :return:

Creates a simple C file to do the type1 exploit :param filename: dumps the code to this path if filename is not None :return:

grab a shellcode with a known name, do not convert it into raw code or template it

Tests if an exploit factory has a type1 exploit.

Tests if an exploit factory has a type2 exploit.

Are we working on a CGC binary?

Are we working on a CGC binary?

Are we working on a Linux binary?

Are we working on a Linux binary?

Determine if the crash can potentially cause an information leak using the point-to-flag technique. :return: True if the 'point-to-f

Write out the exploit in DARPA's POV format. TODO: No value information is accounted for, this will almost always just cause the reg

:param ip: string representing the ip address or domain name to connect back to :param port: port to connect to on the remote host

Save intermediate results (traced states, etc.) to a file to allow faster exploit generation in the future. :param str path: Path

set a new default shellcode

Test the binary generated