MSC16-J. Address the shortcomings of the Singleton design pattern

The singleton design pattern's intent is succinctly described by the seminal work of Gamma et al. [[Gamma 1995]]:

Ensure a class only has one instance, and provide a global point of access to it.

"Since there is only one Singleton instance, any instance fields of a Singleton will occur only once per class, just like static fields. Singletons often control access to resources such as database connections or sockets" [[Fox 2001]]. Other applications of singletons involve maintaining performance statistics, system monitoring and logging, implementing printer spoolers or even ensuring that only one audio file plays at a time. Classes that contain only static methods are good candidates for the singleton pattern.

The Singleton pattern typically uses a single instance of a class that encloses a private static class field. The instance can be created using lazy initialization, which means that the instance is not created when the class loads but when it is first used.

A class designed to hold a singleton object must prevent multiple instantiations of itself from being created. This includes:

• making its constructor private
• employing lock mechanisms to prevent an initialization routine from running simultaneously by multiple threads
• ensuring the class is not serializable
• ensuring the class cannot be cloned
• preventing the class from being garbage-collected if it was loaded by a custom class loader

Noncompliant Code Example (Non-Private Constructor)

This noncompliant code example uses a non-private constructor for instantiating a singleton.

class MySingleton {
  private static MySingleton Instance;

  protected MySingleton() {    
    // private constructor prevents instantiation by untrusted callers
    Instance = new MySingleton();
  }

  public static synchronized MySingleton getInstance() {    
    return Instance;
  }
}

A malicious subclass may extend the accessibility of the constructor from protected to public, allowing untrusted code to create multiple instances of the singleton. Also, the class field Instance has not been declared as final.

Compliant Solution (private Constructor)

This compliant solution reduces the accessibility of the constructor to private and initializes the field Instance immediately, allowing it to be declared final. Singleton constructors must be private.

class MySingleton {
  private static final MySingleton Instance = new MySingleton();

  private MySingleton() {    
    // private constructor prevents instantiation by untrusted callers
  }

  public static synchronized MySingleton getInstance() {    
    return Instance;
  }
}

The MySingleton class need not be declared as final because it has a private constructor.

Noncompliant Code Example (Visibility Across Threads)

If the getter method is tasked with initializing the singleton when necessary, and the getter method is invoked by two (or more) threads simultaneously, multiple instances of the Singleton class might result if access is unsynchronized.

class MySingleton {
  private static MySingleton Instance;

  private MySingleton() {    
    // private constructor prevents instantiation by untrusted callers
  }

  // Lazy initialization
  public static MySingleton getInstance() { // Not synchronized
    if (Instance == null) {
      Instance = new MySingleton();
    }
    return Instance;
  }
}

Consequently, a singleton initializer method in a multithreaded program must employ some form of locking to prevent construction of multiple singleton objects.

Noncompliant Code Example (Inappropriate Synchronization)

Multiple instances can be created even when the singleton construction is encapsulated in a synchronized block.

public static MySingleton getInstance() {
  if (Instance == null) {
    synchronized (MySingleton.class) {
      Instance = new MySingleton();
    }
  }
  return Instance;
}

This is because two or more threads may simultaneously see the field Instance as null in the if condition, and enter the synchronized block one at a time.

Compliant Solution (synchronized Method)

To address the issue of multiple threads creating more than one instance of the singleton, make getInstance() a synchronized method.

class MySingleton {
  private static MySingleton Instance;

  private MySingleton() {
    // private constructor prevents instantiation by untrusted callers
  }

  // Lazy initialization
  public static synchronized MySingleton getInstance() {
    if (Instance == null) {
      Instance = new MySingleton();
    }
    return Instance;
  }
}

Compliant Solution (Double-Checked Locking)

Another compliant solution for implementing thread-safe singletons is the double-checked locking idiom.

class MySingleton {
  private static volatile MySingleton Instance;

  private MySingleton() {
    // private constructor prevents instantiation by untrusted callers
  }

  // Double-checked locking
  public static MySingleton getInstance() {
    if (Instance == null) {
      synchronized (MySingleton.class) {
        if (Instance == null) {
          Instance = new MySingleton();
        }
      }
    }
    return Instance;
  }
}

This design pattern is often implemented incorrectly. Refer to rule [LCK10-J. Do not use incorrect forms of the double-checked locking idiom] for more details on correct use of the double-checked locking idiom.

Compliant Solution (Initialize-On-Demand Holder Class Idiom)

This compliant solution uses a static inner class to create the singleton instance.

class MySingleton {
  static class SingletonHolder {
    static MySingleton Instance = new MySingleton();
  }

  public static MySingleton getInstance() {
    return SingletonHolder.Instance;
  }
}

This is known as the initialize-on-demand holder class idiom. Refer to rule [LCK10-J. Do not use incorrect forms of the double-checked locking idiom] for more information.

Noncompliant Code Example (Serializable)

This noncompliant code example implements the java.io.Serializable interface which allows the class to be serializable. Deserialization of the class implies that multiple instances of the singleton can be created.

class MySingleton implements Serializable {
  private static final long serialVersionUID = 6825273283542226860L;
  private static MySingleton Instance;

  private MySingleton() {
    // private constructor prevents instantiation by untrusted callers
  }

  // Lazy initialization
  public static synchronized MySingleton getInstance() {
    if (Instance == null) {
      Instance = new MySingleton();
    }
    return Instance;
  }
}

A singleton's constructor cannot install checks to enforce the requirement that the number of instances be limited to one because serialization provides a mechanism that bypasses the object's constructor.

Noncompliant Code Example (readResolve() Method)

Adding a readResolve() method that returns the original instance is insufficient to ensure the singleton property. This is insecure even when all the fields are declared transient or static.

class MySingleton implements Serializable {
  private static final long serialVersionUID = 6825273283542226860L;
  private static MySingleton Instance;

  private MySingleton() {
    // private constructor prevents instantiation by untrusted callers
  }

  // Lazy initialization
  public static synchronized MySingleton getInstance() {
    if (Instance == null) {
      Instance = new MySingleton();
    }
    return Instance;
  }

  private Object readResolve() {
    return Instance; 
  }
}

At runtime, an attacker can add a class that reads in a crafted serialized stream:

public class Untrusted implements Serializable {
  public static MySingleton captured;
  public MySingleton capture;
  
  public Untrusted(MySingleton capture) {
    this.capture = capture;
  }

  private void readObject(java.io.ObjectInputStream in) throws Exception {
    in.defaultReadObject();
    captured = capture;
  }
}

The crafted stream an be generated by serializing the following class:

public final class MySingleton implements java.io.Serializable {
  private static final long serialVersionUID = 6825273283542226860L;
  public Untrusted untrusted = new Untrusted(this); // Additional serial field
 
  public MySingleton() { }
}

Upon deserialization, the field MySingleton.untrusted is reconstructed before MySingleton.readResolve() is called. Consequently, Untrusted.captured is assigned the deserialized instance of the crafted stream instead of MySingleton.Instance. This issue is pernicious when an attacker can add classes to exploit the singleton guarantee of an existing serializable class.

Noncompliant Code Example (Non-Transient Instance Fields)

This serializable noncompliant code example uses a non-transient instance field str.

class MySingleton implements Serializable {
  private static final long serialVersionUID = 2787342337386756967L;
  private static MySingleton Instance;
  private String[] str = {"one", "two", "three"}; // non-transient instance field
                 
  private MySingleton() {
    // private constructor prevents instantiation by untrusted callers
  }

  public void displayStr() {
    System.out.println(Arrays.toString(str));
  }
 
  private Object readResolve() {
    return Instance;
  }
}

"If a singleton contains a nontransient object reference field, the contents of this field will be deserialized before the singleton’s readResolve method is run. This allows a carefully crafted stream to "steal" a reference to the originally deserialized singleton at the time the contents of the object reference field are deserialized" [[Bloch 2008]].

Compliant Solution (enum)

Stateful singleton classes must be made non-serializable. As a precautionary measure, classes that are serializable are forbidden to save a reference to a singleton object in their non-transient or non-static instance variables. This prevents the singleton from being indirectly serialized.

Bloch [[Bloch 2008]] suggests the use of an enum type as a replacement for traditional implementations when serializable singletons are indispensable.

public enum MySingleton {
  Instance;
  private String[] str = {"one", "two", "three"}; // non-transient field
     
  public void displayStr() {
    System.out.println(Arrays.toString(str));
  }	 
}

This approach is functionally equivalent to, but much safer than, commonplace implementations. It both ensures that only one instance of the object exists at any instant and also provides the serialization property (because java.lang.Enum<E> extends java.io.Serializable).

Noncompliant Code Example (Cloneable Singleton)

It is also possible to create a copy of the singleton by cloning it using the object's clone() method if the singleton class implements java.lang.Cloneable directly or through inheritance. This noncompliant code example shows a singleton that implements the java.lang.Cloneable interface.

class MySingleton implements Cloneable {
  private static MySingleton Instance;

  private MySingleton() {
    // private constructor prevents instantiation by untrusted callers
  }

  // Lazy initialization
  public static synchronized MySingleton getInstance() {
    if (Instance == null) {
      Instance = new MySingleton();
    }
    return Instance;
  }
}

Compliant Solution (Override clone() Method)

Avoid making the singleton class cloneable by not implementing the Cloneable interface or not deriving from a class that already implements it.

If the singleton class indirectly implements the Cloneable interface through inheritance, the object's clone() method must be overridden with one that throws a CloneNotSupportedException exception [[Daconta 2003]].

class MySingleton implements Cloneable {
  private static MySingleton Instance;

  private MySingleton() {
    // private constructor prevents instantiation by untrusted callers
  }

  // Lazy initialization
  public static synchronized MySingleton getInstance() {
    if (Instance == null) {
      Instance = new MySingleton();
    }
    return Instance;
  }

  public Object clone() throws CloneNotSupportedException {
    throw new CloneNotSupportedException();
  }
}

See rule [OBJ03-J. Sensitive classes must not let themselves be copied] for more details about restricting misuse of the clone() method.

Noncompliant Code Example (Garbage Collection)

When a class is no longer reachable, it is free to be garbage collected. This behavior can be troublesome when the program must maintain the singleton property throughout the entire lifetime of the program.

A static singleton becomes eligible for garbage collection when its class loader becomes eligible for garbage collection. This usually happens when a nonstandard (custom) class loader is used to load the singleton. This noncompliant code example prints different values of the hashcode of the singleton object from different scopes.

  {
    ClassLoader cl1 = new MyClassLoader();
    Class class1 = cl1.loadClass(MySingleton.class.getName());
    Method classMethod = class1.getDeclaredMethod("getInstance", new Class[] { });
    Object singleton = classMethod.invoke(null, new Object[] { });
    System.out.println(singleton.hashCode());
  }
  ClassLoader cl1 = new MyClassLoader();
  Class class1 = cl1.loadClass(MySingleton.class.getName());
  Method classMethod = class1.getDeclaredMethod("getInstance", new Class[] { });
  Object singleton = classMethod.invoke(null, new Object[] { } );
  System.out.println(singleton.hashCode());

Code that is outside the scope can create another instance of the singleton class even though the requirement was to use only the original instance.

Because a singleton instance is associated with the class loader that is used to load it, it is possible to have multiple instances of the same class in the JVM. This typically happens in J2EE containers and applets. Technically, these instances are different classes that are independent of each other. Failing to protect against multiple instances of the singleton may or may not be insecure depending on the specific requirements of the program.

Compliant Solution (Prevent Garbage Collection)

This compliant solution takes into account the garbage collection issue described above. A class cannot be garbage collected until the ClassLoader object used to load it becomes eligible for garbage collection. An easier scheme to prevent the garbage collection is to ensure that there is a direct or indirect reference from a live thread to the singleton object that must be preserved.

This compliant solution demonstrates this technique. It prints a consistent hashcode across all scopes. It uses the ObjectPreserver class based on [[Grand 2002]] and described in rule TSM02-J. Do not use background threads during class initialization.

  {
    ClassLoader cl1 = new MyClassLoader();
    Class class1 = cl1.loadClass(MySingleton.class.getName());
    Method classMethod = class1.getDeclaredMethod("getInstance", new Class[] { });
    Object singleton = classMethod.invoke(null, new Object[] { });
    ObjectPreserver.preserveObject(singleton); // Preserve the object
    System.out.println(singleton.hashCode());
  }
  ClassLoader cl1 = new MyClassLoader();
  Class class1 = cl1.loadClass(MySingleton.class.getName());
  Method classMethod = class1.getDeclaredMethod("getInstance", new Class[] { });
  Object singleton = ObjectPreserver.getObject();  // Retrieve the preserved object
  System.out.println(singleton.hashCode());

Risk Assessment

Using improper forms of the singleton design pattern may lead to creation of multiple instances of the singleton and violate the expected contract of the class.

Related Vulnerabilities

Search for vulnerabilities resulting from the violation of this rule on the CERT website.

Bibliography

[[JLS 2005]] Chapter 17, Threads and Locks
[[Fox 2001]] When is a Singleton not a Singleton? 
[[Daconta 2003]] Item 15: Avoiding Singleton Pitfalls;
[[Darwin 2004]] 9.10 Enforcing the Singleton Pattern
[[Gamma 1995]] Singleton
[[Grand 2002]] Chapter 5, Creational Patterns, Singleton
[[Bloch 2008]] Item 3: "Enforce the singleton property with a private constructor or an enum type" and Item 77: "For instance control, prefer enum types to readResolve"
[[MITRE 2009]] CWE ID 543 "Use of Singleton Pattern Without Synchronization in a Multithreaded Context"

[!The CERT Oracle Secure Coding Standard for Java^button_arrow_left.png!]      [!The CERT Oracle Secure Coding Standard for Java^button_arrow_up.png!]      [!The CERT Oracle Secure Coding Standard for Java^button_arrow_right.png!]