CWE-496: Public Data Assigned to Private Array-Typed Field
Assigning public data to a private array is equivalent to giving public access to the array.
How it's found
Public Data Assigned to Private Array-Typed Field is a specific, narrowly defined instance of a broader pattern. Testers confirm it with targeted code review and a proof-of-concept input that exercises the exact code path this weakness describes.
Consequences
- Modify Application Data: The contents of the array can be modified from outside the intended scope.
Mitigations
- Implementation: Do not allow objects to modify private members of a class.
Where this fits in a TurboPentest engagement
TurboPentest's agentic pentest is powerful and covers a broad range of issues automatically. This particular class is best confirmed in a manual IntegSec engagement, where human pentesters apply deeper methodology and a larger context window than any automated pass.
Frequently asked questions
What is CWE-496?
Assigning public data to a private array is equivalent to giving public access to the array.
How do you find Public Data Assigned to Private Array-Typed Field?
Public Data Assigned to Private Array-Typed Field is a specific, narrowly defined instance of a broader pattern. Testers confirm it with targeted code review and a proof-of-concept input that exercises the exact code path this weakness describes.
What is the impact of CWE-496?
Modify Application Data: The contents of the array can be modified from outside the intended scope.
Does TurboPentest test for Public Data Assigned to Private Array-Typed Field?
TurboPentest's agentic pentest is powerful and covers a broad range of issues automatically. This particular class is best confirmed in a manual IntegSec engagement, where human pentesters apply deeper methodology and a larger context window than any automated pass.
Related CWEs
Find these issues before an attacker does
TurboPentest runs an agentic AI pentest against your target and reports findings with proof, from $99 per target.
Start a $99 pentest