CWE-493: Critical Public Variable Without Final Modifier
CWE版本: 4.18
更新日期: 2025-09-09
弱点描述
The product has a critical public variable that is not final, which allows the variable to be modified to contain unexpected values.
扩展描述
If a field is non-final and public, it can be changed once the value is set by any function that has access to the class which contains the field. This could lead to a vulnerability if other parts of the program make assumptions about the contents of that field.
常见后果
影响范围: Integrity
技术影响: Modify Application Data
说明: The object could potentially be tampered with.
影响范围: Confidentiality
技术影响: Read Application Data
说明: The object could potentially allow the object to be read.
潜在缓解措施
阶段: Implementation
描述: Declare all public fields as final when possible, especially if it is used to maintain internal state of an Applet or of classes used by an Applet. If a field must be public, then perform all appropriate sanity checks before accessing the field from your code.
检测方法
方法: 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 | - | Mobile Code: Non-Final Public Field | - |
| CLASP | - | Failure to provide confidentiality for stored data | - |
| The CERT Oracle Secure Coding Standard for Java (2011) | OBJ10-J | Do not use public static nonfinal variables | - |
| Software Fault Patterns | SFP28 | Unexpected access points | - |