Passing Mutable Objects to an Untrusted Method |
Weakness ID: 375 (Weakness Base) | Status: Draft |
Description Summary
Sending non-cloned mutable data as a return value may result in that data being altered or deleted by the calling function, thereby putting the class in an undefined state.
Scope | Effect |
---|---|
Access Control Integrity | Potentially data could be tampered with by another function which should not have been tampered with. |
Example 1
(Bad Code)
Example Languages: C and C++
private: externalClass foo; public: void doStuff() {
//..//Modify foo
return foo;
}
(Bad Code)
Example Language: Java
public class foo {
private externalClass bar = new externalClass();
public doStuff(...){
//..//Modify bar
return bar;
}
Phase: Implementation Pass in data which should not be altered as constant or immutable. |
Phase: 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. |
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. |
Nature | Type | ID | Name | View(s) this relationship pertains to![]() |
---|---|---|---|---|
ChildOf | ![]() | 371 | State Issues | Development Concepts (primary)699 |
ChildOf | ![]() | 668 | Exposure of Resource to Wrong Sphere | Research Concepts (primary)1000 |
Mapped Taxonomy Name | Node ID | Fit | Mapped Node Name |
---|---|---|---|
CLASP | Passing mutable objects to an untrusted method |
Submissions | ||||
---|---|---|---|---|
Submission Date | Submitter | Organization | Source | |
CLASP | Externally Mined | |||
Modifications | ||||
Modification Date | Modifier | Organization | Source | |
2008-07-01 | Eric Dalci | Cigital | External | |
updated Time of Introduction | ||||
2008-09-08 | CWE Content Team | MITRE | Internal | |
updated Applicable Platforms, Common Consequences, Relationships, Other Notes, Taxonomy Mappings |