...
- A memory leak
- An infinite loop
- Limited amounts of default heap memory available
- Incorrect implementation of common data structures (hash tables, vectors and so on)
- Unbound deserialization
- Upon writing a large number of objects to an
ObjectOutputStream
Noncompliant Code Example
This noncompliant code example places no upper bounds on the memory space required to execute the program. Consequently, the program can easily exhaust the heap.
Code Block | ||
---|---|---|
| ||
public class ShowHeapError { Vector<String> names = new Vector<String>(); InputStreamReader input = new InputStreamReader(System.in); BufferedReader reader = new BufferedReader(input); public void addNames() throws IOException { while(true) { // Adding unknown number of records to a list; user can exhaust the heap String newName = reader.readLine(); if(!newName.equalsIgnoreCase("quit")) { // Enter "quit" to quit the program names.addElement(newName); } else { break; } } // Close "reader" and "input" } public static void main(String[] args) throws IOException { ShowHeapError demo = new ShowHeapError(); demo.addNames(); } } |
Compliant Solution
If the objects or data structures are large enough to potentially cause heap exhaustion, the programmer must consider using databases instead.
To remedy the noncompliant code example, the user can reuse a single long
variable to store the input and write that value into a database containing a table User
, with a field userID
along with any other required fields. This prevents the heap from getting exhausted.
Noncompliant Code Example
Wiki Markup |
---|
This noncompliant code example requires more memory on the heap than is available by default. In a server-class machine using a parallel garbage collector, the default initial and maximum heap sizes are as follows for J2SE 6.0 \[[Sun 06|AA. Java References#Sun 06]\]: |
...
Code Block | ||
---|---|---|
| ||
/** Assuming the heap size as 512 MB (calculated as 1/4th of 2 GB RAM = 512 MB) * Considering long values being entered (64 bits each, the max number of elements * would be 512 MB/64bits = 67108864) */ public class ShowHeapError { Vector<Long> names = new Vector<Long>(); // Accepts unknown number of records long newID = 0L; int count = 67108865; int i = 0; InputStreamReader input = new InputStreamReader(System.in); Scanner reader = new Scanner(input); public void addNames(){ do{ // Adding unknown number of records to a list // The user can enter more number of IDs than what the heap can support and // exhaust the heap. Assume that the record ID is a 64 bit long value System.out.print("Enter recordID (To quit, enter -1): "); newID = reader.nextLong(); names.addElement(newID); i++; }while (i < count || newID != -1); // Close "reader" and "input" } public static void main(String[] args) { ShowHeapError demo = new ShowHeapError(); demo.addNames(); } } |
Compliant Solution
Wiki Markup |
---|
The {{OutOfMemoryError}} can be avoided by making sure that there are no infinite loops, memory leaks or unnecessary object retention. If memory requirements are known ahead of time, the heap size in Java can be tailored to fit the requirements using the following runtime parameters \[[Java 06|AA. Java References#Java 06]\]: |
...
This setting can be changed either using the Java Control Panel or from the command line. It cannot be adjusted through the application itself.
Noncompliant Code Example
Wiki Markup |
---|
According to the Java API \[[API 06|AA. Java References#API 06]\], Class {{ObjectInputStream}} documentation: |
...
Code Block | ||
---|---|---|
| ||
FileOutputStream fos = new FileOutputStream("data.txt"); ObjectOutputStream oos = new ObjectOutputStream(fos); oos.writeObject(new Date()); // ... |
Compliant Solution (3)
If heap related issues arise, it is recommended that the ObjectOutputStream.reset()
method be called so that references to previously written objects may be garbage collected.
Code Block | ||
---|---|---|
| ||
FileOutputStream fos = new FileOutputStream("data.txt"); ObjectOutputStream oos = new ObjectOutputStream(fos); oos.writeObject(new Date()); oos.reset(); // Reset the Object-Handle table to its initial state // ... |
Risk Assessment
Assuming that infinite heap space is available can result in denial of service.
Rule | Severity | Likelihood | Remediation Cost | Priority | Level |
---|---|---|---|---|---|
MSC07- J | low | probable | medium | P4 | L3 |
Related Vulnerabilities
Search for vulnerabilities resulting from the violation of this rule on the CERT website
Other Languages
This rule appears in the C Secure Coding Standard as MEM11-C. Do not assume infinite heap space.
This rule appears in the C++ Secure Coding Standard as MEM12-CPP. Do not assume infinite heap space.
Related Vulnerabilities
References
Wiki Markup |
---|
\[[Sun 06|AA. Java References#Sun 06]\] [Garbage Collection Ergonomics|http://java.sun.com/javase/6/docs/technotes/guides/vm/gc-ergonomics.html ], "Default values for the Initial and Maximum heap size" \[[Java 06|AA. Java References#Java 06]\] [java - the Java application launcher|http://java.sun.com/javase/6/docs/technotes/tools/windows/java.html ], "Syntax for increasing the heap size" \[[Sun 03|AA. Java References#Sun 03]\] Chapter 5: Tuning the Java Runtime System, [Tuning the Java Heap|http://docs.sun.com/source/817-2180-10/pt_chap5.html#wp57027] \[[API 06|AA. Java References#API 06]\] Class ObjectInputStream and ObjectOutputStream \[[SDN 08|AA. Java References#SDN 08]\] [Serialization FAQ|http://java.sun.com/javase/technologies/core/basic/serializationFAQ.jsp] \[[MITRE 09|AA. Java References#MITRE 09]\] [CWE ID 400|http://cwe.mitre.org/data/definitions/400.html] "Uncontrolled Resource Consumption (aka 'Resource Exhaustion')" |
...