CWE-96Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection')

Description

The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before inserting the input into an executable resource, such as a library, configuration file, or template.

Common consequences

• Confidentiality→Read Files or Directories,Read Application Data
  The injected code could access restricted data / files.
• Access Control→Bypass Protection Mechanism
  In some cases, injectable code controls authentication; this may lead to a remote vulnerability.
• Access Control→Gain Privileges or Assume Identity
  Injected code can access resources that the attacker is directly prevented from accessing.
• Integrity,Confidentiality,Availability,Other→Execute Unauthorized Code or Commands
  Code injection attacks can lead to loss of data integrity in nearly all cases as the control-plane data injected is always incidental to data recall or writing. Additionally, code injection can often result in the execution of arbitrary cod
• Non-Repudiation→Hide Activities
  Often the actions performed by injected control code are unlogged.

Potential mitigations

• Implementation
  [object Object]
• Implementation
  Perform proper output validation and escaping to neutralize all code syntax from data written to code files.

Related CWEs

Recent CVEs classified under this CWE