Difference between revisions of "Publicizing of private data when using inner classes"

Jump to: navigation, search
Line 2: Line 2:
[[ASDR Table of Contents]]
[[ASDR Table of Contents]]

Revision as of 07:47, 19 February 2009

This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.

ASDR Table of Contents

Last revision (mm/dd/yy): 02/19/2009


Java byte code has no notion of an inner class; therefore inner classes provide only a package-level security mechanism. Furthermore, the inner class gets access to the fields of its outer class even if that class is declared private.


  • Confidentiality: "Inner Classes" data confidentiality aspects can often be overcome.

Exposure period

Implementation: This is a simple logical flaw created at implementation time.


  • Languages: Java
  • Operating platforms: Any

Required resources




Likelihood of exploit


A common misconception by Java programmers is that inner classes can only be accessed by outer classes. Inner classes' main function is to reduce the size and complexity of code. This can be trivially broken by injecting byte code into the package. Furthermore, since an inner class has access to all fields in the outer class - even if the outer class is private - potentially access to the outer classes fields could be accidently compromised.

Risk Factors



In Java:

private class Secure(){
   private password="mypassword"
   public class Insecure(){...}

Related Attacks

Related Vulnerabilities

Related Controls

  • Implementation: Using sealed classes protects object-oriented encapsulation paradigms and therefore protects code from being extended in unforeseen ways.
  • Implementation: Inner Classes do not provide security. Warning: Never reduce the security of the object from an outer class, going to an inner class. If your outer class is final or private, ensure that your inner class is private as well.

Related Technical Impacts