CWE-462 상세 정보

Duplicate keys in associative lists can lead to non-unique keys being mistaken for an error.

배경 세부 정보

취약점 도입 방식

Implementation : Duplicate key entries could be inserted by mistake, introducing an ambiguity.

적용 가능한 플랫폼

언어

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

일반적인 결과

잠재적 완화 방법

Phases : Implementation
Use a hash table instead of an alist.
Phases : Implementation
Use an alist which checks the uniqueness of hash keys with each entry before inserting the entry.
Phases : Implementation
Duplicate key entries in an association list are not recommended and should not be allowed.

탐지 방법

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.

참고 자료

REF-18

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

REF-1539

We Checked the Android Source Code by PVS-Studio, or Nothing is Perfect
Andrey Karpov.
https://pvs-studio.com/en/blog/posts/cpp/0579/

제출

수정 사항