Latest revision as of 20:41, 20 February 2009

Description

Sending non-cloned mutable data as a return value may result in that data being altered or deleted by the called function, thereby putting the class in an undefined state.

Consequences

Access Control / Integrity: Potentially data could be tampered with by another function which should not have been tampered with.

Exposure period

Implementation: This flaw is a simple logic issue, introduced entirely at implementation time.

Platform

Languages: C,C++ or Java

Operating platforms: Any

Required resources

Any

Severity

Medium

Likelihood of exploit

Medium

In situations where functions return references to mutable data, it is possible that this external code, which called the function, may make changes to the data sent. If this data was not previously cloned, you will be left with modified data which may, or may not, be valid in the context of the class in question.

Risk Factors

Talk about the factors that make this vulnerability likely or unlikely to actually happen

Discuss the technical impact of a successful exploit of this vulnerability

Implementation: Pass in data which should not be alerted as constant or immutable.

Implementation: Clone all mutable data before returning references to it. This is the preferred mitigation. This way, regardless of what changes are made to the data, a valid copy is retained for use by the class.