Exécuter une analyse statique (SAST) sur le code source à la recherche du motif non sécurisé dans le flux de données.
CWE-96 Base Brouillon
Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection')
Static Code Injection occurs when an application incorporates unvalidated or improperly sanitized user input directly into a static, executable resource like a configuration file, template, or…
Définition
What is CWE-96?
Static Code Injection occurs when an application incorporates unvalidated or improperly sanitized user input directly into a static, executable resource like a configuration file, template, or library. Because this input is saved and later executed, it allows an attacker to inject malicious code that becomes a permanent part of the application's logic.
This vulnerability is dangerous because the injected code becomes embedded within a file that the system trusts and executes automatically. Unlike attacks that only affect a single transaction, a successful static code injection can persistently compromise the application, leading to ongoing data theft, system takeover, or service disruption every time the compromised resource is used.
To prevent it, developers must treat all data destined for static files as untrusted. Implement strict input validation using allowlists for expected values and context-specific output encoding or sanitization before writing data to configuration files, templates, or scripts. Never construct executable code by simply concatenating user input.
Impact réel
Real-world CVEs caused by CWE-96
-
Perl code directly injected into CGI library file from parameters to another CGI program.
-
Direct PHP code injection into supporting template file.
-
Direct code injection into PHP script that can be accessed by attacker.
-
PHP code from User-Agent HTTP header directly inserted into log file implemented as PHP script.
-
chain: execution after redirect allows non-administrator to perform static code injection.
Comment les attaquants l'exploitent
Parcours de l'attaquant étape par étape
- 1
This example attempts to write user messages to a message file and allow users to view them.
- 2
While the programmer intends for the MessageFile to only include data, an attacker can provide a message such as:
- 3
which will decode to the following:
- 4
The programmer thought they were just including the contents of a regular data file, but PHP parsed it and executed the code. Now, this code is executed any time people view messages.
- 5
Notice that XSS (CWE-79) is also possible in this situation.
Exemple de code vulnérable
Vulnerable PHP
This example attempts to write user messages to a message file and allow users to view them.
$MessageFile = "messages.out";
if ($_GET["action"] == "NewMessage") {
$name = $_GET["name"];
$message = $_GET["message"];
$handle = fopen($MessageFile, "a+");
fwrite($handle, "<b>$name</b> says '$message'<hr>\n");
fclose($handle);
echo "Message Saved!<p>\n";
}
else if ($_GET["action"] == "ViewMessages") {
include($MessageFile);
} Charge utile de l'attaquant
While the programmer intends for the MessageFile to only include data, an attacker can provide a message such as:
name=h4x0r
message=%3C?php%20system(%22/bin/ls%20-l%22);?%3E Exemple de code sécurisé
Secure pseudo
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
const safe = validateAndEscape(input);
return executeWithGuards(safe);
} What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Liste de contrôle de prévention
How to prevent CWE-96
- Implementation Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
- Implementation Perform proper output validation and escaping to neutralize all code syntax from data written to code files.
Signaux de détection
How to detect CWE-96
Exécuter des tests de sécurité applicative dynamique (DAST) contre le point de terminaison en ligne.
Surveiller les journaux runtime pour détecter des traces d'exception inhabituelles, des entrées malformées ou des tentatives de contournement d'autorisation.
Revue de code : signaler tout nouveau code qui traite les entrées de cette surface sans utiliser les helpers du framework validés.
Plexicus détecte automatiquement CWE-96 et ouvre une PR de correction en moins de 60 secondes.
Codex Remedium analyse chaque commit, identifie cette faiblesse précise et livre une pull request prête à être relue avec le correctif. Pas de tickets. Pas de transferts.
Questions fréquentes Qu'est-ce que CWE-96 ?
Quelle est la gravité de CWE-96 ?
Quels langages ou plateformes sont affectés par CWE-96 ?
Comment puis-je prévenir CWE-96 ?
Comment Plexicus détecte et corrige CWE-96 ?
Où puis-je en savoir plus sur CWE-96 ?
Frequently asked questions
Qu'est-ce que CWE-96 ?
Static Code Injection occurs when an application incorporates unvalidated or improperly sanitized user input directly into a static, executable resource like a configuration file, template, or library. Because this input is saved and later executed, it allows an attacker to inject malicious code that becomes a permanent part of the application's logic.
Quelle est la gravité de CWE-96 ?
MITRE n'a pas publié de note de probabilité d'exploitation pour cette faiblesse. Traitez-la comme un impact moyen jusqu'à ce que votre modèle de menace prouve le contraire.
Quels langages ou plateformes sont affectés par CWE-96 ?
MITRE lists the following affected platforms: PHP, Perl, Interpreted.
Comment puis-je prévenir CWE-96 ?
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and…
Comment Plexicus détecte et corrige CWE-96 ?
Le moteur SAST de Plexicus reconnaît la signature de flux de données de CWE-96 à chaque commit. Lorsqu'une correspondance est trouvée, notre agent Codex Remedium ouvre une PR de correction avec le code corrigé, les tests et un résumé d'une ligne pour le relecteur.
Où puis-je en savoir plus sur CWE-96 ?
MITRE publie la définition canonique à https://cwe.mitre.org/data/definitions/96.html. Vous pouvez également consulter la documentation OWASP et NIST pour des conseils adjacents.
Faiblesses associées
Weaknesses related to CWE-96
CWE-94 Parent
Improper Control of Generation of Code ('Code Injection')
This vulnerability occurs when an application builds executable code using unvalidated external input, such as user data. Because the…
CWE-1336 Frère
Improper Neutralization of Special Elements Used in a Template Engine
This vulnerability occurs when an application uses a template engine to process user-controlled input but fails to properly sanitize…
CWE-95 Frère
Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')
This vulnerability occurs when an application takes user input and passes it directly into a dynamic code execution function, like eval(),…
CWE-97 Enfant
Improper Neutralization of Server-Side Includes (SSI) Within a Web Page
This vulnerability occurs when a web application dynamically generates pages but fails to properly sanitize user-supplied input that could…
Prêt quand vous l'êtes
Arrêtez de payer par développeur.
Commencez à fermer la boucle.
Plexicus est l'ASPM natif IA qui scanne, filtre, corrige, penteste et explique — de façon autonome. Développeurs illimités, dépôts illimités, actions IA à usage équitable. Vrai niveau gratuit, €269/mo annuel quand vous êtes prêt.