CWEweakness
CWE-496 Public Data Assigned to Private Array-Typed Field
- Abstraction
- Variant
- Structure
- Simple
- Status
- Incomplete
- Languages
- C, C#, C++, Java, Object-Oriented
- CWE version
- 5.0
Description
Assigning public data to a private array is equivalent to giving public access to the array.
Common consequences
• Integrity: Modify Application Data — The contents of the array can be modified from outside the intended scope.
Potential mitigations
• [Implementation] Do not allow objects to modify private members of a class.
Detection methods
• 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.)
Related
Child of · CWE (1)
- CWE-668 Exposure of Resource to Wrong Sphere weakness
Referenced by CWE · has member (1)
- CWE-884 CWE Cross-section view