Page History

Wiki Markup According to the The Java Language Specification \[[JLS 2005|AA. Bibliography#JLS 05]\], Section 12, §12.5, "Creation of New Class Instances," [JLS 2015]:

Unlike C++, the Java programming language does not specify altered rules for method dispatch during the creation of a new class instance. If methods are invoked that are overridden in subclasses in the object being initialized, then these overriding methods are used, even before the new object is completely initialized.

Consequently, invocation Invocation of an overridable method during object construction may result in the use of uninitialized data, leading to runtime exceptions or to unanticipated outcomes. Calling overridable methods from constructors can also leak the this reference before object construction is complete, potentially exposing uninitialized or inconsistent data to other threads . See rule (see TSM01-J. Do not let the ( this ) reference escape during object construction for additional information). As a result, constructors may invoke a class's constructor must invoke (directly or indirectly) only methods in that class that are static, final or private; all other method invocations are forbidden.

Noncompliant Code Example

This noncompliant code example results in the use of uninitialized data by the doLogic() method.:

class SuperClass {
  public SuperClass () {
    doLogic();
  }

  public void doLogic() {
    System.out.println("This is superclass!");
  }
}

class SubClass extends SuperClass {
  private String color = null;
  public SubClass() {
    super();
    color = "Redred";
  }

  public void doLogic() {
    // Color becomes null
    System.out.println("This is subclass! The color is :" + color);
    // ...
  }
}

public class Overridable {
  public static void main(String[] args) {
    SuperClass bc = new SuperClass();
    // Prints "This is superclass!"
    SuperClass sc = new SubClass();
    // Prints "This is subclass! The color is :null"
  }
}

...

This compliant solution declares the doLogic() method as final so that it cannot be overridden.:

class SuperClass {
  public SuperClass() {
    doLogic();
  }

  public final void doLogic() {
    System.out.println("This is superclass!");
  }
}

...

Allowing a constructor to call overridable methods may give can provide an attacker with access to the this reference before an object is fully initialized, which in turn could lead to a vulnerability.

Automated Detection

Automated detection of constructors that contain invocations of overridable methods appears to be is straightforward.

Related Vulnerabilities

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

Bibliography

Related Guidelines

Bibliography

...

Image Removed      05. Methods (MET)      Image Added Image Added