CWE-546 상세 정보

The code contains comments that suggest the presence of bugs, incomplete functionality, or weaknesses.

취약점 도입 방식

Implementation : If the code is missing security functionality or checking, developers might add suspicious comments such as BUG, HACK, FIXME, LATER, LATER2, or TODO. The code could have other problems that programmers should fix, such as hard-coded variables, error handling, not using stored procedures, and performance issues.

적용 가능한 플랫폼

언어

클래스: Not Language-Specific (Undetermined)

일반적인 결과

잠재적 완화 방법

Phases : Documentation
Remove comments that suggest the presence of bugs, incomplete functionality, or weaknesses, before deploying the application.

탐지 방법

Automated Static Analysis

Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

취약점 매핑 메모

근거 : 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.

제출

수정 사항