{
	"id": "ce7f8f00-9b01-493f-975d-2384074cf615",
	"created_at": "2026-04-06T00:19:35.576039Z",
	"updated_at": "2026-04-10T13:12:03.944935Z",
	"deleted_at": null,
	"sha1_hash": "39e603a251fd0e14efa6847cf1df3eb84d08b36f",
	"title": "CAPEC-641: DLL Side-Loading (Version 3.9)",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 41926,
	"plain_text": "CAPEC-641: DLL Side-Loading (Version 3.9)\r\nArchived: 2026-04-05 14:20:49 UTC\r\n Description\r\nAn adversary places a malicious version of a Dynamic-Link Library (DLL) in the Windows Side-by-Side (WinSxS)\r\ndirectory to trick the operating system into loading this malicious DLL instead of a legitimate DLL. Programs specify the\r\nlocation of the DLLs to load via the use of WinSxS manifests or DLL redirection and if they aren't used then Windows\r\nsearches in a predefined set of directories to locate the file. If the applications improperly specify a required DLL or WinSxS\r\nmanifests aren't explicit about the characteristics of the DLL to be loaded, they can be vulnerable to side-loading.\r\n Likelihood Of Attack\r\n Typical Severity\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\n Prerequisites\r\nThe target must fail to verify the integrity of the DLL before using them.\r\n Skills Required\r\n[Level: High]\r\nTrick the operating system in loading a malicious DLL instead of a legitimate DLL.\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\nIntegrity\r\nExecute Unauthorized Commands\r\nBypass Protection Mechanism\r\n Mitigations\r\nPrevent unknown DLLs from loading through using an allowlist policy.\r\nPatch installed applications as soon as new updates become available.\r\nProperly restrict the location of the software being used.\r\nUse of sxstrace.exe on Windows as well as manual inspection of the manifests.\r\nRequire code signing and avoid using relative paths for resources.\r\nhttps://capec.mitre.org/data/definitions/641.html\r\nPage 1 of 2\n\nTaxonomy 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\n1574.002 Hijack Execution Flow:DLL Side-Loading\r\n References\r\n Content History\r\nSubmissions\r\nSubmission Date Submitter Organization\r\n2018-07-31\r\n(Version 2.12)\r\nCAPEC Content Team The MITRE Corporation\r\nModifications\r\nModification Date Modifier Organization\r\n2019-04-04\r\n(Version 3.1)\r\nCAPEC Content Team The MITRE Corporation\r\nUpdated Taxonomy_Mappings\r\n2020-07-30\r\n(Version 3.3)\r\nCAPEC Content Team The MITRE Corporation\r\nUpdated Mitigations, Taxonomy_Mappings\r\nMore information is available — Please select a different filter.\r\nSource: https://capec.mitre.org/data/definitions/641.html\r\nhttps://capec.mitre.org/data/definitions/641.html\r\nPage 2 of 2",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"origins": [
		"web"
	],
	"references": [
		"https://capec.mitre.org/data/definitions/641.html"
	],
	"report_names": [
		"641.html"
	],
	"threat_actors": [],
	"ts_created_at": 1775434775,
	"ts_updated_at": 1775826723,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/39e603a251fd0e14efa6847cf1df3eb84d08b36f.pdf",
		"text": "https://archive.orkl.eu/39e603a251fd0e14efa6847cf1df3eb84d08b36f.txt",
		"img": "https://archive.orkl.eu/39e603a251fd0e14efa6847cf1df3eb84d08b36f.jpg"
	}
}