Exécuter une analyse statique (SAST) sur le code source à la recherche du motif non sécurisé dans le flux de données.
CWE-1116 Base Incomplet
Inaccurate Comments
This weakness occurs when code comments do not correctly describe or explain the actual behavior of the associated code. Misleading comments create a disconnect between what the documentation says…
Définition
What is CWE-1116?
This weakness occurs when code comments do not correctly describe or explain the actual behavior of the associated code. Misleading comments create a disconnect between what the documentation says and what the program actually does.
Inaccurate comments introduce confusion and inefficiency during code reviews and security audits. Reviewers must spend extra time verifying actual behavior against stated intent, slowing down the validation process and increasing the risk that subtle logic errors or security flaws will be overlooked.
Over time, this inconsistency makes code maintenance significantly harder, indirectly harming security. It becomes more difficult to identify root causes of bugs or vulnerabilities, and developers are more likely to introduce new defects when modifying code they do not fully understand due to misleading documentation.
Impact réel
Real-world CVEs caused by CWE-1116
Aucune référence CVE publique n'est liée à ce CWE dans le catalogue MITRE pour le moment.
Comment les attaquants l'exploitent
Parcours de l'attaquant étape par étape
- 1
In the following Java example the code performs a calculation to determine how much medicine to administer. A comment is provided to give insight into what the calculation shoud be doing. Unfortunately the comment does not match the actual code and thus leaves the reader to wonder which is correct.
- 2
In the correction below, the code functionality has been verified, and the comment has been corrected to reflect the proper calculation.
- 3
Note that in real-world code, these values should be validated to disallow negative numbers, prevent integer overflow, etc.
Exemple de code vulnérable
Vulnerable Java
In the following Java example the code performs a calculation to determine how much medicine to administer. A comment is provided to give insight into what the calculation shoud be doing. Unfortunately the comment does not match the actual code and thus leaves the reader to wonder which is correct.
public class Main {
```
public static void main(String[] args) {
int pt_weight = 83;
int mg_per_kg = 3;
int daily_dose = 0;
// Add the patient weight and Mg/Kg to calculate the correct daily dose
daily_dose = pt_weight * mg_per_kg;
return dosage;
}
} Exemple de code sécurisé
Secure Java
In the correction below, the code functionality has been verified, and the comment has been corrected to reflect the proper calculation.
public class Main {
```
public static void main(String[] args) {
int pt_weight = 83;
int mg_per_kg = 3;
int daily_dose = 0;
// Multiply the patient weight and Mg/Kg to calculate the correct daily dose
daily_dose = pt_weight * mg_per_kg;
return dosage;
}
} 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-1116
- Implementation Verify that each comment accurately reflects what is intended to happen during execution of the code.
Signaux de détection
How to detect CWE-1116
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.
CWE-1116
Don't catalog this weakness. Prove it's reachable.
Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.
Questions fréquentes Qu'est-ce que CWE-1116 ?
Quelle est la gravité de CWE-1116 ?
Quels langages ou plateformes sont affectés par CWE-1116 ?
Comment puis-je prévenir CWE-1116 ?
Comment Plexicus détecte et corrige CWE-1116 ?
Où puis-je en savoir plus sur CWE-1116 ?
Frequently asked questions
Qu'est-ce que CWE-1116 ?
This weakness occurs when code comments do not correctly describe or explain the actual behavior of the associated code. Misleading comments create a disconnect between what the documentation says and what the program actually does.
Quelle est la gravité de CWE-1116 ?
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-1116 ?
MITRE n'a pas spécifié les plateformes affectées pour ce CWE — il peut s'appliquer à la plupart des stacks applicatives.
Comment puis-je prévenir CWE-1116 ?
Verify that each comment accurately reflects what is intended to happen during execution of the code.
Comment Plexicus détecte et corrige CWE-1116 ?
Le moteur SAST de Plexicus reconnaît la signature de flux de données de CWE-1116 à 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-1116 ?
MITRE publie la définition canonique à https://cwe.mitre.org/data/definitions/1116.html. Vous pouvez également consulter la documentation OWASP et NIST pour des conseils adjacents.
Faiblesses associées
Weaknesses related to CWE-1116
CWE-1078 Parent
Inappropriate Source Code Style or Formatting
This weakness occurs when source code violates established style guidelines for formatting, indentation, whitespace, or commenting, making…
CWE-1085 Frère
Invokable Control Element with Excessive Volume of Commented-out Code
This weakness occurs when a callable function, method, or procedure contains a large amount of inactive, commented-out code within its…
CWE-1099 Frère
Inconsistent Naming Conventions for Identifiers
This weakness occurs when a codebase uses mixed naming styles for elements like variables, functions, data types, or files, creating an…
CWE-1106 Frère
Insufficient Use of Symbolic Constants
This weakness occurs when developers embed raw numbers or text strings directly in code instead of using named symbolic constants, making…
CWE-1107 Frère
Insufficient Isolation of Symbolic Constant Definitions
This weakness occurs when a codebase uses symbolic constants (like named values for numbers or strings) but scatters their definitions…
CWE-1109 Frère
Use of Same Variable for Multiple Purposes
This weakness occurs when a single variable is reused to handle multiple, unrelated tasks or to store different pieces of data throughout…
CWE-1113 Frère
Inappropriate Comment Style
This weakness occurs when source code comments are written in a style or format that doesn't match the project's established standards or…
CWE-1114 Frère
Inappropriate Whitespace Style
This weakness occurs when source code uses inconsistent or non-standard whitespace formatting, such as irregular indentation, spacing, or…
CWE-1115 Frère
Source Code Element without Standard Prologue
This weakness occurs when source code files or modules lack a consistent, standardized header or prologue that the development team has…
Ressources
Further reading
Prêt à valider l'essentiel ?
Prêt à valider ce qui compte.
Plexicus est Proof-Driven AppSec : findings validés, compréhension contextuelle et remédiation relue — ancrée dans la preuve, scopée avec vous.