CWE-462
Duplicate Key in Associative List (Alist)
Description
Duplicate keys in associative lists can lead to non-unique keys being mistaken for an error.
A duplicate key entry -- if the alist is designed properly -- could be used as a constant time replace function. However, duplicate key entries could be inserted by mistake. Because of this ambiguity, duplicate key entries in an association list are not recommended and should not be allowed.
Parent Weaknesses (ChildOf)
Common Consequences
Scope
Impact
Quality Degradation, Varies by Context
Potential Mitigations
Use a hash table instead of an alist.
Use an alist which checks the uniqueness of hash keys with each entry before inserting the entry.
Applicable Platforms
Security Training
Train your team to recognize and prevent security threats with our comprehensive security awareness program.
Start TrainingVulnerability Scanning
Discover vulnerabilities in your applications and infrastructure before attackers do.
Scan Now