05. Methods (MET)

Guidelines

• Page:
  MET00-J. Validate method arguments
• Page:
  MET01-J. Never use assertions to validate method arguments
• Page:
  MET02-J. Do not use deprecated or obsolete classes or methods
• Page:
  MET03-J. Methods that perform a security check must be declared private or final
• Page:
  MET04-J. Do not increase the accessibility of overridden or hidden methods
• Page:
  MET05-J. Ensure that constructors do not call overridable methods
• Page:
  MET06-J. Do not invoke overridable methods in clone()
• Page:
  MET07-J. Never declare a class method that hides a method declared in a superclass or superinterface
• Page:
  MET08-J. Preserve the equality contract when overriding the equals() method
• Page:
  MET09-J. Classes that define an equals() method must also define a hashCode() method
• Page:
  MET10-J. Follow the general contract when implementing the compareTo() method
• Page:
  MET11-J. Ensure that keys used in comparison operations are immutable
• Page:
  MET12-J. Do not use finalizers
• Page:
  MET13-J. Do not assume that reassigning method arguments modifies the calling environment
• Page:
  MET50-J. Avoid ambiguous or confusing uses of overloading
• Page:
  MET51-J. Do not use overloaded methods to differentiate between runtime types
• Page:
  MET52-J. Do not use the clone() method to copy untrusted method parameters
• Page:
  MET53-J. Ensure that the clone() method calls super.clone()
• Page:
  MET54-J. Always provide feedback about the resulting value of a method
• Page:
  MET55-J. Return an empty array or collection instead of a null value for methods that return an array or collection
• Page:
  MET56-J. Do not use Object.equals() to compare cryptographic keys
• Page:
  Rec. 06. Methods (MET)
• Page:
  Rule 06. Methods (MET)

Risk Assessment Summary

OBJ14-J. Defensively copy mutable inputs and mutable internal components      The CERT Oracle Secure Coding Standard for Java      MET01-J. Validate method parameters