CWE-546: Suspicious Comment
The code contains comments that suggest the presence of bugs, incomplete functionality, or weaknesses.
Last updated
Overview
Many suspicious comments, such as BUG, HACK, FIXME, LATER, LATER2, TODO, in the code indicate missing security functionality and checking. Others indicate code problems that programmers should fix, such as hard-coded variables, error handling, not using stored procedures, and performance issues.
Common consequences
What can happen when CWE-546 is exploited.
Quality Degradation
Affects: Other
Suspicious comments could be an indication that there are problems in the source code that may need to be fixed and is an indication of poor quality. This could lead to further bugs and the introduction of weaknesses.
How it happens
When it is introduced
Typically introduced during these phases of the software lifecycle.
How to prevent it
Practical mitigations for CWE-546, grouped by where in the lifecycle they apply.
Remove comments that suggest the presence of bugs, incomplete functionality, or weaknesses, before deploying the application.