CWE-1284 상세 정보

The product receives input that is expected to specify a quantity (such as size or length), but it does not validate or incorrectly validates that the quantity has the required properties.

취약점 도입 방식

Implementation : Code may rely on specified quantities to allocate resources, perform calculations, control iteration, etc. Since quantities are often used to affect resource allocation or process financial data, they are often present in many places in the code.

적용 가능한 플랫폼

언어

클래스: Not Language-Specific (Often)

일반적인 결과

관찰된 예시

잠재적 완화 방법

Phases : Implementation

탐지 방법

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 Base 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.

메모

This entry is still under development and will continue to see updates and content improvements.

제출

수정 사항