Software vulnerabilities detection system and methods

A method of detecting software vulnerabilities by a microprocessor executing program instructions stored on a computer-readable non-transitory storage medium, said method comprising the steps of:

• (a) inputting compiled code;
• (b) creating an instruction model for each said instruction, said instruction model comprising instruction location, debug information, instruction type, operands, existing memory state requirements, basic block membership, function/method membership and class membership of each said instruction;
• (c) creating a control flow graph associated with each said instruction model, said control flow graph comprising all potential control flow paths and a bidirectional list of predecessor instructions for each said instruction;
• (d) creating and populating a data flow model comprising recorded flow of unsafe data as observed during the execution of said compiled code;
• (e) analyzing said instruction model, said control flow graph and said data flow model to create a security finding for each said instruction that calls an unsafe function on unsafe data;
• and
• (f) generating a security report comprising information related to each said security finding, wherein said security report further comprises an execution trace of said unsafe data corresponding to each said security finding, said execution trace comprising information from the origin to the termination of said unsafe data.

A method of detecting software vulnerabilities by a microprocessor executing program instructions stored on a computer-readable non-transitory storage medium, said method comprising the steps of:

• (a) inputting compiled code and source code that resulted in said compiled code;
• (b) creating an instruction model for each said instruction, said instruction model comprising instruction location, debug information, instruction type, operands, existing memory state requirements, and basic block membership of each said instruction;
• (c) creating a control flow graph associated with each said instruction model, said control flow graph comprising all potential control flow paths for each said instruction;
• (d) creating and populating a data flow model comprising recorded flow of unsafe data as observed during execution of said compiled code;
• (e) analyzing said instruction model, said control flow graph and said data flow model to create a security finding for each said instruction that calls an unsafe function on unsafe data;
• and
• (f) creating a security finding for each said instruction that calls an unsafe function on unsafe data, wherein said security report further comprises an execution trace of said unsafe data corresponding to each said security finding, said execution trace comprising information from the origin to the termination of said unsafe data.