背景详情
引入方式
Implementation : Duplicate key entries could be inserted by mistake, introducing an ambiguity.
适用平台
编程语言
名称: C (Undetermined)
名称: C++ (Undetermined)
名称: Java (Undetermined)
名称: C# (Undetermined)
常见后果
| 影响范围 |
影响 |
可能性 |
| Other | Quality Degradation, Varies by Context
注意: If an alist contains duplicate key entries, this introduces an ambiguity in which it cannot be predicted which key value will be selected. | |
潜在缓解措施
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/
提交记录
| 名称 |
组织 |
日期 |
发布日期 |
Version |
| CLASP |
|
2006-07-19 +00:00 |
2006-07-19 +00:00 |
Draft 3 |
修改记录
| 名称 |
组织 |
日期 |
备注 |
| Eric Dalci |
Cigital |
2008-07-01 +00:00 |
updated Time_of_Introduction |
| CWE Content Team |
MITRE |
2008-09-08 +00:00 |
updated Applicable_Platforms, Relationships, Other_Notes, Taxonomy_Mappings |
| CWE Content Team |
MITRE |
2008-11-24 +00:00 |
updated Relationships, Taxonomy_Mappings |
| CWE Content Team |
MITRE |
2009-10-29 +00:00 |
updated Demonstrative_Examples, Description, Other_Notes |
| CWE Content Team |
MITRE |
2011-06-01 +00:00 |
updated Common_Consequences |
| CWE Content Team |
MITRE |
2011-06-27 +00:00 |
updated Common_Consequences |
| CWE Content Team |
MITRE |
2011-09-13 +00:00 |
updated Relationships, Taxonomy_Mappings |
| CWE Content Team |
MITRE |
2012-05-11 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2014-07-30 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2017-11-08 +00:00 |
updated Taxonomy_Mappings |
| CWE Content Team |
MITRE |
2020-02-24 +00:00 |
updated References, Relationships |
| CWE Content Team |
MITRE |
2023-04-27 +00:00 |
updated Relationships, Time_of_Introduction, Type |
| CWE Content Team |
MITRE |
2023-06-29 +00:00 |
updated Mapping_Notes |
| CWE Content Team |
MITRE |
2025-12-11 +00:00 |
updated Weakness_Ordinalities |
| CWE Content Team |
MITRE |
2026-10-28 +00:00 |
updated Background_Details, Common_Consequences, Description, Detection_Factors, Modes_of_Introduction, Potential_Mitigations, References |