CWE-494Download of Code Without Integrity Check

Description

Common consequences· 1

• Integrity / Availability / Confidentiality / Other — Execute Unauthorized Code or Commands, Alter Execution Logic, Other
  Executing untrusted code could compromise the control flow of the program. The untrusted code could execute attacker-controlled commands, read or modify sensitive resources, or prevent the software from functioning correctly for legitimate users.

Potential mitigations· 5

• [Implementation]Perform proper forward and reverse DNS lookups to detect DNS spoofing.
• [Architecture and Design, Operation]
• [Architecture and Design]
• [Architecture and Design, Operation]Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.
• [Architecture and Design, Operation]

Related CAPEC attack patterns· 12

Exploits (incoming)12

Compliance frameworks addressing this (incoming)2

(incoming)31

Showing top 30 of 31 by confidence. Click any target to see the full neighbourhood.

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.