CWE-496
Weakness AllowedPublic Data Assigned to Private Array-Typed Field
Abstraction: Variant · Status: Incomplete
Assigning public data to a private array is equivalent to giving public access to the array.
Mapping guidance
This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
Modes of introduction
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.)
Effectiveness: High
Content history
added/updated demonstrative examples
updated Time_of_Introduction
added/updated white box definitions
updated Applicable_Platforms, Relationships, Taxonomy_Mappings
updated Common_Consequences
updated Common_Consequences, Relationships
updated Potential_Mitigations
updated Relationships, Taxonomy_Mappings
updated Relationships, White_Box_Definitions
updated References, Relationships
updated Detection_Factors, Relationships
updated Mapping_Notes
updated Applicable_Platforms, Weakness_Ordinalities
updated References, Relationships
0 vulnerabilities reference this CWE, most recent first.
No vulnerabilities reference this CWE.
Mitigation
Do not allow objects to modify private members of a class.
No CAPEC attack patterns related to this CWE.