Suspicious Comment
Draft Variant
Structure: Simple
Description
The code contains comments that suggest the presence of bugs, incomplete functionality, or weaknesses.
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 1
Scope: Other
Impact: Quality Degradation
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.
Potential Mitigations 1
Phase: Documentation
Remove comments that suggest the presence of bugs, incomplete functionality, or weaknesses, before deploying the application.
Demonstrative Examples 1
The following excerpt demonstrates the use of a suspicious comment in an incomplete code block that may have security repercussions.
Code Example:
Bad
Java
java// TODO: Handle null user condition.* }
Applicable Platforms
Languages:
Not Language-Specific : Undetermined
Modes of Introduction
Implementation
Related Weaknesses