Dark Mode

Settings

Capec-188 Detail

Reverse Engineering

Meta Software Physical Security Hardware Likelihood: Low Typical Severity: Low

Children: 167 189

Threats: T60 T291

Description

An adversary discovers the structure, function, and composition of an object, resource, or system by using a variety of analysis techniques to effectively determine how the analyzed entity was constructed or operates. The goal of reverse engineering is often to duplicate the function, or a part of the function, of an object in order to duplicate or "back engineer" some aspect of its functioning. Reverse engineering techniques can be applied to mechanical objects, electronic devices, or software, although the methodology and techniques involved in each type of analysis differ widely.

Not present

External ID Source Link Description
CAPEC-188 capec https://capec.mitre.org/data/definitions/188.html
CWE-1278 cwe http://cwe.mitre.org/data/definitions/1278.html
REF-50 reference_from_CAPEC http://en.wikipedia.org/wiki/Reverse_engineering Wikipedia, The Wikimedia Foundation, Inc

Not present

  1. Access to targeted system, resources, and information.
  1. The technical resources necessary to engage in reverse engineering differ in accordance with the type of object, resource, or system being analyzed.
High
Understanding of low level programming languages or technologies can be very helpful. For example, when reverse engineering a binary file, an understanding of assembly languages can help to determine the purpose and inner-workings of the code. Another example is reverse engineering an application that relies on networking. Here, an understanding networking protocols can provide insight into application details.

Not present

  1. When adversaries are reverse engineering software, methodologies fall into two broad categories, 'white box' and 'black box.' White box techniques involve methods which can be applied to a piece of software when an executable or some other compiled object can be directly subjected to analysis, revealing at least a portion of its machine instructions that can be observed upon execution. 'Black Box' methods involve interacting with the software indirectly, in the absence of the ability to measure, instrument, or analyze an executable object directly. Such analysis typically involves interacting with the software at the boundaries of where the software interfaces with a larger execution environment, such as input-output vectors, libraries, or APIs.