# US 2012/0254839 A1 · Simulating black box test results using information from white box testing

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0254839 A1
- Document ID: US20120254839A1
- Status: Published application
- Kind: A1
- Application number: 13/493,067
- Filed: 2012-06-11
- Published: 2012-10-04
- Earliest claimed: 2010-10-27
- Assignees: International Business Machines Corporation
- Inventors: Stephen Fink; Yinnon A. Haviv; Roee Hay; Marco Pistoia; Ory Segal; Adi Sharabani; Manu Sridharan; Frank Tip; Omer Tripp; Omri Weisman
- Web page: https://patentgrep.com/patent/US20120254839A1

## CPC

- G06F 11/3604: Analysis of software for verifying properties of programs (testing of software G06F11/3668)
- G06F 9/44589: {Program code verification, e.g. Java bytecode verification, proof-carrying code (high-level semantic checks G06F8/43; prevention of errors by analysis, debugging or testing of software G06F11/36)}
- G06F 9/455: Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F 11/36: Prevention of errors by analysis, debugging or testing of software
- G06F 11/362: Debugging of software
- G06F 21/577: {Assessing vulnerabilities and evaluating computer system security}
- G06F 2221/033: Test or assess software
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems, methods are program products for simulating black box test results using information obtained from white box testing, including analyzing computer software (e.g., an application) to identify a potential vulnerability within the computer software application and a plurality of milestones associated with the potential vulnerability, where each of the milestones indicates a location within the computer software application, tracing a path from a first one of the milestones to an entry point into the computer software application, identifying an input to the entry point that would result in a control flow from the entry point and through each of the milestones, describing the potential vulnerability in a description indicating the entry point and the input, and presenting the description via a computer-controlled output medium.

## Claims

### Claim 1

A method, comprising:
analyzing computer software to identify a potential vulnerability within the computer software and a plurality of milestones associated with the potential vulnerability, wherein each of the milestones indicates a location within the computer software;
tracing a path from a first one of the milestones to an entry point into the computer software;
identifying an input to the entry point that would result in a control flow from the entry point and through each of the milestones;
describing the potential vulnerability in a description indicating the entry point and the input; and
presenting the description via a computer-controlled output medium.

### Claim 2 (depends on 1)

The method of claim 1 wherein analyzing comprises analyzing each of the milestones to identify any constraints the milestone places on the input in order to allow the control flow to reach the milestone given the input.

### Claim 3 (depends on 1)

The method of claim 1 wherein the computer software is an application.

### Claim 4

A method, comprising:
analyzing computer software to identify a potential vulnerability within the computer software and a plurality of milestones associated with the potential vulnerability, wherein each of the milestones indicates a location within the computer software;
tracing a path from a first one of the milestones to an entry point into the computer software, wherein the entry point is a location within the computer software where an interface is exposed to receive the input to the computer software from a source that is external to the computer software;
identifying an input to the entry point that would result in a control flow from the entry point and through each of the milestones;
describing the potential vulnerability in a description indicating the entry point and the input; and
presenting the description via a computer-controlled output medium.

### Claim 5 (depends on 4)

The method of claim 4 wherein analyzing comprises analyzing each of the milestones to identify any constraints the milestone places on the input in order to allow the control flow to reach the milestone given the input.

### Claim 6 (depends on 4)

The method of claim 4 wherein the computer software is an application.

### Claim 7

A method, comprising:
analyzing computer software to identify a potential vulnerability within the computer software and a plurality of milestones associated with the potential vulnerability, wherein each of the milestones indicates a location within the computer software;
tracing a path from a first one of the milestones to an entry point into the computer software, wherein tracing comprises constructing a call graph of method invocations within the computer software and utilizing the call graph to trace the path;
identifying an input to the entry point that would result in a control flow from the entry point and through each of the milestones;
describing the potential vulnerability in a description indicating the entry point and the input; and
presenting the description via a computer-controlled output medium.

### Claim 8 (depends on 7)

The method of claim 7 wherein the analyzing step comprises analyzing each of the milestones to identify any constraints the milestone places on the input in order to allow the control flow to reach the milestone given the input.

### Claim 9 (depends on 7)

The method of claim 7 wherein the computer software is an application.
