CWE-481 상세 정보

The code uses an operator for assignment when the intention was to perform a comparison.

취약점 도입 방식

Implementation : In many languages, the compare statement is very close in appearance to the assignment statement and are often confused. This bug is generally the result of a typo. This usually causes obvious problems with program execution. If the comparison is in an "if" statement, the if statement will usually evaluate the value of the right-hand side of the predicate. As a result, this weakness might only go undetected if there's insufficient testing and rarely-reached code paths.

적용 가능한 플랫폼

언어

이름: C (Undetermined)
이름: C++ (Undetermined)
이름: Java (Undetermined)
이름: C# (Undetermined)

일반적인 결과

잠재적 완화 방법

Phases : Implementation
Place constants on the left. If one attempts to assign a constant with a variable, the compiler will produce an error.

탐지 방법

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.)
효과성 : High

Automated Static Analysis - Source Code

An Integrated Development Environment (IDE) or linter can report or highlight this weakness.

취약점 매핑 메모

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

참고 자료

REF-18

The CLASP Application Security Process
Secure Software, Inc..
https://cwe.mitre.org/documents/sources/TheCLASPApplicationSecurityProcess.pdf

REF-62

The Art of Software Security Assessment
Mark Dowd, John McDonald, Justin Schuh.

제출

수정 사항