{
	"id": "3412accc-3dae-4239-aec9-dfbd78ae2730",
	"created_at": "2026-04-06T00:20:01.482692Z",
	"updated_at": "2026-04-10T03:20:57.613154Z",
	"deleted_at": null,
	"sha1_hash": "2411d3b868e0416159037e138c41a7de244203a4",
	"title": "CAPEC-639: Probe System Files (Version 3.9)",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 43872,
	"plain_text": "CAPEC-639: Probe System Files (Version 3.9)\r\nArchived: 2026-04-05 21:33:40 UTC\r\nAttack Pattern ID: 639\r\nAbstraction: Detailed\r\n Description\r\nAn adversary obtains unauthorized information due to improperly protected files. If an application stores sensitive\r\ninformation in a file that is not protected by proper access control, then an adversary can access the file and search for\r\nsensitive information.\r\n Typical Severity\r\nMedium\r\n Relationships\r\nThis table shows the other attack patterns and high level categories that are related to this attack pattern. These\r\nrelationships are defined as ChildOf and ParentOf, and give insight to similar items that may exist at higher and lower levels\r\nof abstraction. In addition, relationships such as CanFollow, PeerOf, and CanAlsoBe are defined to show similar attack\r\npatterns that the user may want to explore.\r\nNature Type\r\nChildOf Standard Attack Pattern - A standard level attack pattern in CAPEC is focused on a specific methodology or technique used in an attack. It\r\nThis table shows the views that this attack pattern belongs to and top level categories within that view.\r\nView Name Top Level Categories\r\nDomains of Attack Software\r\nMechanisms of Attack Collect and Analyze Information\r\n Prerequisites\r\nAn adversary has access to the file system of a system.\r\n Consequences\r\nThis table specifies different individual consequences associated with the attack pattern. The Scope identifies the security\r\nproperty that is violated, while the Impact describes the negative technical impact that arises if an adversary succeeds in\r\ntheir attack. The Likelihood provides information about how likely the specific consequence is expected to be seen relative\r\nto the other consequences in the list. For example, there may be high likelihood that a pattern will be used to achieve a\r\ncertain impact, but a low likelihood that it will be exploited to achieve a different impact.\r\nScope Impact Likelihood\r\nConfidentiality Read Data\r\n Mitigations\r\nVerify that files have proper access controls set, and reduce the storage of sensitive information to only what is necessary.\r\n Example Instances\r\nAdversaries may search local file systems and remote file shares for files containing passwords. These can be files\r\ncreated by users to store their own credentials, shared credential stores for a group of individuals, configuration files\r\ncontaining passwords for a system or service, or source code/binary files containing embedded passwords.\r\nhttps://capec.mitre.org/data/definitions/639.html\r\nPage 1 of 2\n\nAdversaries may search network shares on computers they have compromised to find files of interest.\r\n Taxonomy Mappings\r\nCAPEC mappings to ATT\u0026CK techniques leverage an inheritance model to streamline and minimize direct\r\nCAPEC/ATT\u0026CK mappings. Inheritance of a mapping is indicated by text stating that the parent CAPEC has relevant\r\nATT\u0026CK mappings. Note that the ATT\u0026CK Enterprise Framework does not use an inheritance model as part of the\r\nmapping to CAPEC.\r\nRelevant to the ATT\u0026CK taxonomy mapping (also see parent)\r\nEntry ID Entry Name\r\n1039 Data from Network Shared Drive\r\n1552.001 Unsecured Credentials: Credentials in Files\r\n1552.003 Unsecured Credentials: Bash History\r\n1552.004 Unsecured Credentials: Private Keys\r\n1552.006 Unsecured Credentials: Group Policy Preferences\r\n Content History\r\nSubmissions\r\nSubmission Date Submitter Organization\r\n2018-05-04\r\n(Version 2.11)\r\nCAPEC Content Team The MITRE Corporation\r\nModifications\r\nModification Date Modifier Organization\r\n2020-07-30\r\n(Version 3.3)\r\nCAPEC Content Team The MITRE Corporation\r\nUpdated Related_Attack_Patterns, Taxonomy_Mappings\r\n2022-09-29\r\n(Version 3.8)\r\nCAPEC Content Team The MITRE Corporation\r\nUpdated Taxonomy_Mappings\r\nMore information is available — Please select a different filter.\r\nSource: https://capec.mitre.org/data/definitions/639.html\r\nhttps://capec.mitre.org/data/definitions/639.html\r\nPage 2 of 2",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"references": [
		"https://capec.mitre.org/data/definitions/639.html"
	],
	"report_names": [
		"639.html"
	],
	"threat_actors": [],
	"ts_created_at": 1775434801,
	"ts_updated_at": 1775791257,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/2411d3b868e0416159037e138c41a7de244203a4.pdf",
		"text": "https://archive.orkl.eu/2411d3b868e0416159037e138c41a7de244203a4.txt",
		"img": "https://archive.orkl.eu/2411d3b868e0416159037e138c41a7de244203a4.jpg"
	}
}