CAPEC-150: Collect Data from Common Resource Locations
Description
An adversary exploits well-known locations for resources for the purposes of undermining the security of the target. In many, if not most systems, files and resources are organized in a default tree structure. This can be useful for adversaries because they often know where to look for resources or files that are necessary for attacks. Even when the precise location of a targeted resource may not be known, naming conventions may indicate a small area of the target machine's file tree where the resources are typically located. For example, configuration files are normally stored in the /etc director on Unix systems. Adversaries can take advantage of this to commit other types of attacks.
- Likelihood of attack
- Not rated by MITRE
- Typical severity
- Medium
- Abstraction
- StandardA specific methodology or technique used in an attack.
Mechanism of attack: Collect and Analyze Information
Prerequisites
- The targeted applications must either expect files to be located at a specific location or, if the location of the files can be configured by the user, the user either failed to move the files from the default location or placed them in a conventional location for files of the given type.
Mitigations
CAPEC 3.9 lists no mitigation for this pattern; see its child patterns or related weaknesses.
Related weaknesses (CWE)
- CWE-552Files or Directories Accessible to External Parties
- CWE-1239Improper Zeroization of Hardware Register
- CWE-1258Exposure of Sensitive System Information Due to Uncleared Debug Information
- CWE-1266Improper Scrubbing of Sensitive Data from Decommissioned Device
- CWE-1272Sensitive Information Uncleared Before Debug/Power State Transition
- CWE-1323Improper Management of Sensitive Trace Data
- CWE-1330Remanent Data Readable after Memory Erase
ATT&CK techniques (CAPEC taxonomy mapping)
Across MITRE's defensive frameworks
Linked through the 6 ATT&CK techniques above.
Counter with D3FEND
Defensive techniques MITRE D3FEND maps to the same ATT&CK techniques.
- D3-RDRestore Database3 shared
- D3-DIData Inventory3 shared
- D3-CFContent Filtering3 shared
- D3-CMContent Modification3 shared
- D3-DFDecoy File3 shared
- D3-FAFile Analysis3 shared
- D3-FEFile Encryption3 shared
- D3-FEVFile Eviction3 shared
- D3-FIMFile Integrity Monitoring3 shared
- D3-LFPLocal File Permissions3 shared
- D3-RFAMRemote File Access Mediation3 shared
- D3-RFRestore File3 shared
Detect with CAR
MITRE CAR analytics that cover the same ATT&CK techniques.
- CAR-2019-04-004Credential Dumping via Mimikatz1 shared
- CAR-2019-07-002Lsass Process Dump via Procdump1 shared
- CAR-2019-08-001Credential Dumping via Windows Task Manager1 shared
- CAR-2019-08-002Active Directory Dumping via NTDSUtil1 shared
- CAR-2020-05-001MiniDump of LSASS1 shared
- CAR-2021-05-011Create Remote Thread into LSASS1 shared
- CAR-2013-07-001Suspicious Arguments1 shared
- CAR-2013-04-002Quick execution of a series of suspicious commands1 shared
Related attack patterns
Parent
More specific patterns
- CAPEC-143Detect Unpublicized Web PagesDetailed
- CAPEC-144Detect Unpublicized Web ServicesDetailed
- CAPEC-155Screen Temporary Files for Sensitive InformationDetailed
- CAPEC-406Dumpster DivingDetailed
- CAPEC-637Collect Data from ClipboardDetailed
- CAPEC-647Collect Data from RegistriesDetailed
- CAPEC-648Collect Data from Screen CaptureDetailed