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.
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| ChildOf | Prohibited | C | 1078 | Inappropriate Source Code Style or Formatting |
| ParentOf | Allowed | V | 615 | Inclusion of Sensitive Information in Source Code Comments |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | V | 884 | CWE Cross-section |
| MemberOf | Prohibited | C | 963 | SFP Secondary Cluster: Exposed Data |
| MemberOf | Prohibited | C | 1412 | Comprehensive Categorization: Poor Coding Practices |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | BS | BOSS-294 | Not Language-Specific Weaknesses |
| MemberOf | Prohibited | BS | BOSS-325 | Quality Degradation (impact) |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 963 | SFP Secondary Cluster: Exposed Data |
| Scope | Likelihood | Impact | Note |
|---|---|---|---|
| Other | N/A | 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. |
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.
Remove comments that suggest the presence of bugs, incomplete functionality, or weaknesses, before deploying the application.
N/A
The following excerpt demonstrates the use of a suspicious comment in an incomplete code block that may have security repercussions.
| Reference | Description |
|---|
| Ordinality | Description |
|---|---|
| Indirect | N/A |
This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
| Taxonomy Name | Entry ID | Fit | Entry Name |
|---|
| ID | Name |
|---|