Description
The product has a method that is declared public, but returns a reference to a private data structure, which could then be modified in unexpected ways.
Modes of Introduction:
– Implementation
Related Weaknesses
Consequences
Integrity: Modify Application Data
The contents of the data structure can be modified from outside the intended scope.
Potential Mitigations
Phase: Implementation
Description:
Declare the method private.
Phase: Implementation
Description:
Clone the member data and keep an unmodified version of the data private to the object.
Phase: Implementation
Description:
Use public setter methods that govern how a private member can be modified.
CVE References
More Stories
The Most Dangerous Vulnerabilities in Apache Tomcat and How to Protect Against Them
Apache Tomcat is an open-source web server and servlet container that is widely used in enterprise environments to run Java...
ZDI-CAN-18333: A Critical Zero-Day Vulnerability in Microsoft Windows
Zero-day vulnerabilities are a serious threat to cybersecurity, as they can be exploited by malicious actors to gain unauthorized access...
CWE-669 – Incorrect Resource Transfer Between Spheres
Description The product does not properly transfer a resource/behavior to another sphere, or improperly imports a resource/behavior from another sphere,...
CWE-67 – Improper Handling of Windows Device Names
Description The software constructs pathnames from user input, but it does not handle or incorrectly handles a pathname containing a...
CWE-670 – Always-Incorrect Control Flow Implementation
Description The code contains a control flow path that does not reflect the algorithm that the path is intended to...
CWE-671 – Lack of Administrator Control over Security
Description The product uses security features in a way that prevents the product's administrator from tailoring security settings to reflect...