Insufficient Encapsulation
This weakness occurs when a software component exposes too much of its internal workings, such as data structures or implementation logic. This lack of proper boundaries allows other parts of the system to interact with it in unintended ways, potentially leading to corrupted data, unexpected behavior, or hidden dependencies.
Insufficient encapsulation creates a fragile codebase where changes in one module can have unpredictable ripple effects across the system. This directly increases maintenance costs and complexity, as developers must spend extra time tracing these unintended couplings instead of focusing on core functionality or security fixes. From a security perspective, this architectural flaw indirectly introduces risk. It becomes harder to identify and patch vulnerabilities because the code's behavior is less predictable and more scattered. Furthermore, the constant need to work around these exposed internals makes it easier for developers to accidentally introduce new security bugs during routine maintenance or feature development.
ID : DX-212
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.Code Example:
c++// if the username and password in the input parameters are equal to*
c++c++Code Example:
c++