结构: Simple
Abstraction: Variant
状态: Incomplete
被利用可能性: unkown
The software declares a critical variable, field, or member to be public when intended security policy requires it to be private.
This issue makes it more difficult to maintain the software, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities. It also might make it easier to introduce vulnerabilities.
Language: [{'cwe_Name': 'C++', 'cwe_Prevalence': 'Undetermined'}, {'cwe_Name': 'C#', 'cwe_Prevalence': 'Undetermined'}, {'cwe_Name': 'Java', 'cwe_Prevalence': 'Undetermined'}]
范围 | 影响 | 注释 |
---|---|---|
['Integrity', 'Confidentiality'] | ['Read Application Data', 'Modify Application Data'] | Making a critical variable public allows anyone with access to the object in which the variable is contained to alter or read the value. |
Other | Reduce Maintainability |
策略:
Data should be private, static, and final whenever possible. This will assure that your code is protected by instantiating early, preventing access, and preventing tampering.
The following example declares a critical variable public, making it accessible to anyone with access to the object in which it is contained.
bad C++
Instead, the critical data should be declared private.
good C++
Even though this example declares the password to be private, there are other possible issues with this implementation, such as the possibility of recovering the password from process memory (CWE-257).
The following example shows a basic user account class that includes member variables for the username and password as well as a public constructor for the class and a public method to authorize access to the user account.
bad C++
However, the member variables username and password are declared public and therefore will allow access and changes to the member variables to anyone with access to the object. These member variables should be declared private as shown below to prevent unauthorized access and changes.
good C++
标识 | 说明 | 链接 |
---|---|---|
映射的分类名 | ImNode ID | Fit | Mapped Node Name |
---|---|---|---|
CLASP | Failure to protect stored data from modification | ||
The CERT Oracle Secure Coding Standard for Java (2011) | OBJ01-J | Declare data members as private and provide accessible wrapper methods | |
Software Fault Patterns | SFP28 | Unexpected access points | |
OMG ASCMM | ASCMM-MNT-15 |