CAPECattack pattern
CAPEC-37 Retrieve Embedded Sensitive Data
Very High
Official page ↗
- Abstraction
- Detailed
- Status
- Draft
- Likelihood of attack
- High
- Typical severity
- Very High
- CAPEC version
- 3.9
Description
An attacker examines a target system to find sensitive data that has been embedded within it. This information can reveal confidential contents, such as account numbers or individual keys/credentials that can be used as an intermediate step in a larger attack.
Execution flow
1. [Explore] [Identify Target] Attacker identifies client components to extract information from. These may be binary executables, class files, shared libraries (e.g., DLLs), configuration files, or other system files.
2. [Exploit] [Retrieve Embedded Data] The attacker then uses a variety of techniques, such as sniffing, reverse-engineering, and cryptanalysis to retrieve the information of interest.
Prerequisites
• In order to feasibly execute this type of attack, some valuable data must be present in client software.
• Additionally, this information must be unprotected, or protected in a flawed fashion, or through a mechanism that fails to resist reverse engineering, statistical, or other attack.
Skills required
• [Medium] The attacker must possess knowledge of client code structure as well as ability to reverse-engineer or decompile it or probe it in other ways. This knowledge is specific to the technology and language used for the client distribution
Consequences
• Confidentiality: Read Data
• Integrity: Modify Data
• Confidentiality, Access Control, Authorization: Gain Privileges
Related
Att&ck technique · MITRE ATT&CK (2)
Child of · CAPEC (1)
- CAPEC-167 White Box Reverse Engineering attack pattern
Weakness · CWE (14)
- CWE-1239 Improper Zeroization of Hardware Register weakness
- CWE-1258 Exposure of Sensitive System Information Due to Uncleared Debug Information weakness
- CWE-1266 Improper Scrubbing of Sensitive Data from Decommissioned Device weakness
- CWE-1272 Sensitive Information Uncleared Before Debug/Power State Transition weakness
- CWE-1278 Missing Protection Against Hardware Reverse Engineering Using Integrated Circuit (IC) Imaging Techniques weakness
- CWE-1301 Insufficient or Incomplete Data Removal within Hardware Component weakness
- CWE-1330 Remanent Data Readable after Memory Erase weakness
- CWE-226 Sensitive Information in Resource Not Removed Before Reuse weakness
- CWE-311 Missing Encryption of Sensitive Data weakness
- CWE-312 Cleartext Storage of Sensitive Information weakness
- CWE-314 Cleartext Storage in the Registry weakness
- CWE-315 Cleartext Storage of Sensitive Information in a Cookie weakness
- CWE-318 Cleartext Storage of Sensitive Information in Executable weakness
- CWE-525 Use of Web Browser Cache Containing Sensitive Information weakness
Referenced by CAPEC · can precede (2)
Referenced by CWE · attack pattern (14)
- CWE-1239 Improper Zeroization of Hardware Register weakness
- CWE-1258 Exposure of Sensitive System Information Due to Uncleared Debug Information weakness
- CWE-1266 Improper Scrubbing of Sensitive Data from Decommissioned Device weakness
- CWE-1272 Sensitive Information Uncleared Before Debug/Power State Transition weakness
- CWE-1278 Missing Protection Against Hardware Reverse Engineering Using Integrated Circuit (IC) Imaging Techniques weakness
- CWE-1301 Insufficient or Incomplete Data Removal within Hardware Component weakness
- CWE-1330 Remanent Data Readable after Memory Erase weakness
- CWE-226 Sensitive Information in Resource Not Removed Before Reuse weakness
- CWE-311 Missing Encryption of Sensitive Data weakness
- CWE-312 Cleartext Storage of Sensitive Information weakness
- CWE-314 Cleartext Storage in the Registry weakness
- CWE-315 Cleartext Storage of Sensitive Information in a Cookie weakness
- CWE-318 Cleartext Storage of Sensitive Information in Executable weakness
- CWE-525 Use of Web Browser Cache Containing Sensitive Information weakness