CWE-486: Comparison of Classes by Name
CWE版本: 4.18
更新日期: 2025-09-09
弱点描述
The product compares classes by name, which can cause it to use the wrong class when multiple classes can have the same name.
扩展描述
If the decision to trust the methods and data of an object is based on the name of a class, it is possible for malicious users to send objects of the same name as trusted classes and thereby gain the trust afforded to known classes and types.
常见后果
影响范围: Integrity Confidentiality Availability
技术影响: Execute Unauthorized Code or Commands
说明: If a product relies solely on the name of an object to determine identity, it may execute the incorrect or unintended code.
潜在缓解措施
阶段: Implementation
描述: Use class equivalency to determine type. Rather than use the class name to determine if an object is of a given type, use the getClass() method, and == operator.
检测方法
方法: 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
引入模式
| 阶段 | 说明 |
|---|---|
| Implementation | - |
适用平台
编程语言
分类映射
| 分类名称 | 条目ID | 条目名称 | 映射适配度 |
|---|---|---|---|
| 7 Pernicious Kingdoms | - | Comparing Classes by Name | - |
| CLASP | - | Comparing classes by name | - |
| The CERT Oracle Secure Coding Standard for Java (2011) | OBJ09-J | Compare classes and not class names | - |
| Software Fault Patterns | SFP1 | Glitch in computation | - |