CWEweakness

CWE-495 Private Data Structure Returned From A Public Method

Official page ↗
Abstraction
Variant
Structure
Simple
Status
Draft
Languages
C, C#, C++, Java, Object-Oriented
CWE version
5.0

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.

Common consequences

• Integrity: Modify Application Data — The contents of the data structure can be modified from outside the intended scope.

Potential mitigations

• [Implementation] Declare the method private. • [Implementation] Clone the member data and keep an unmodified version of the data private to the object. • [Implementation] Use public setter methods that govern how a private member can be modified.

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 CVE · weakness (1)

  • CVE-2025-29868 Private Data Structure Returned From A Public Method vulnerability in Apache Answer. vulnerability

Referenced by CWE · has member (1)