CWE-492 Variant Draft Medium likelihood

Use of Inner Class Containing Sensitive Data

Using inner classes to handle sensitive data can unintentionally expose that data because of how Java compiles them. The compiler transforms inner classes into separate, package-visible classes,…

Definition

What is CWE-492?

Using inner classes to handle sensitive data can unintentionally expose that data because of how Java compiles them. The compiler transforms inner classes into separate, package-visible classes, which can bypass the intended private access restrictions.

Inner classes in Java create hidden security risks due to their compilation process. While your source code might declare an inner class as private to its enclosing class, the Java bytecode has no built-in support for this relationship. To make it work, the compiler converts the inner class into a separate peer class with package-level access. This means code you intended to keep private within a single class becomes accessible to all other classes in the same package. This becomes especially dangerous because inner classes can access private fields of their outer class. To allow this access in the transformed bytecode, the compiler silently changes those private fields to protected scope. As a result, sensitive data you marked as private can be exposed through the newly created peer class, breaking your intended encapsulation and creating a potential data leak.

Real-world impact

Real-world CVEs caused by CWE-492

No public CVE references are linked to this CWE in MITRE's catalog yet.

How attackers exploit it

Step-by-step attacker path

1
The following Java Applet code mistakenly makes use of an inner class.
2
The following example shows a basic use of inner classes. The class OuterClass contains the private member inner class InnerClass. The private inner class InnerClass includes the method concat that accesses the private member variables of the class OuterClass to output the value of one of the private member variables of the class OuterClass and returns a string that is a concatenation of one of the private member variables of the class OuterClass, the separator input parameter of the method and the private member variable of the class InnerClass.
3
Although this is an acceptable use of inner classes it demonstrates one of the weaknesses of inner classes that inner classes have complete access to all member variables and methods of the enclosing class even those that are declared private and protected. When inner classes are compiled and translated into Java bytecode the JVM treats the inner class as a peer class with package level access to the enclosing class.
4
To avoid this weakness of inner classes, consider using either static inner classes, local inner classes, or anonymous inner classes.
5
The following Java example demonstrates the use of static inner classes using the previous example. The inner class InnerClass is declared using the static modifier that signifies that InnerClass is a static member of the enclosing class OuterClass. By declaring an inner class as a static member of the enclosing class, the inner class can only access other static members and methods of the enclosing class and prevents the inner class from accessing nonstatic member variables and methods of the enclosing class. In this case the inner class InnerClass can only access the static member variable memberTwo of the enclosing class OuterClass but cannot access the nonstatic member variable memberOne.

Vulnerable code example

Vulnerable Java

The following Java Applet code mistakenly makes use of an inner class.

Vulnerable Java

public final class urlTool extends Applet {
  	private final class urlHelper {
  		...
  	}
  	...
  }

Secure code example

Secure Java

The following Java example demonstrates the use of static inner classes using the previous example. The inner class InnerClass is declared using the static modifier that signifies that InnerClass is a static member of the enclosing class OuterClass. By declaring an inner class as a static member of the enclosing class, the inner class can only access other static members and methods of the enclosing class and prevents the inner class from accessing nonstatic member variables and methods of the enclosing class. In this case the inner class InnerClass can only access the static member variable memberTwo of the enclosing class OuterClass but cannot access the nonstatic member variable memberOne.

Secure Java

public class OuterClass {
```
// private member variables of OuterClass* 
  		private String memberOne;
  		private static String memberTwo;
  		
  		
  		 *// constructor of OuterClass* 
  		public OuterClass(String varOne, String varTwo) {
  		
  		```
  			this.memberOne = varOne;
  			this.memberTwo = varTwo;
  		}
```
// InnerClass is a static inner class of OuterClass* 
  		private static class InnerClass {
  		```
  				private String innerMemberOne;
  				public InnerClass(String innerVarOne) {
  					this.innerMemberOne = innerVarOne;
  				}
  				public String concat(String separator) {
```
// InnerClass only has access to static member variables of OuterClass* 
  						return memberTwo + separator + this.innerMemberOne;}}}

What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.

Prevention checklist

How to prevent CWE-492

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 an outer class is final or private, ensure that its inner class is private as well.

Detection signals

How to detect CWE-492

Automated Static Analysis High

Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

Plexicus auto-fix

Plexicus auto-detects CWE-492 and opens a fix PR in under 60 seconds.

Codex Remedium scans every commit, identifies this exact weakness, and ships a reviewer-ready pull request with the patch. No tickets. No hand-offs.

Get a demo Try Plexicus free

Frequently asked questions

What is CWE-492?

How serious is CWE-492?

MITRE rates the likelihood of exploit as Medium — exploitation is realistic but typically requires specific conditions.

What languages or platforms are affected by CWE-492?

MITRE lists the following affected platforms: Java.

How can I prevent CWE-492?

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

How does Plexicus detect and fix CWE-492?

Plexicus's SAST engine matches the data-flow signature for CWE-492 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.

Where can I learn more about CWE-492?

MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/492.html. You can also reference OWASP and NIST documentation for adjacent guidance.

Related weaknesses

Weaknesses related to CWE-492

CWE-668 Parent

Don't Let Security
Weigh You Down.

Stop choosing between AI velocity and security debt. Plexicus is the only platform that runs Vibe Coding Security and ASPM in parallel — one workflow, every codebase.

Use of Inner Class Containing Sensitive Data

What is CWE-492?

Real-world CVEs caused by CWE-492

Step-by-step attacker path

Vulnerable Java

Secure Java

How to prevent CWE-492

How to detect CWE-492

Plexicus auto-detects CWE-492 and opens a fix PR in under 60 seconds.

Frequently asked questions

Weaknesses related to CWE-492

Exposure of Resource to Wrong Sphere

Improper Isolation of Shared Resources on System-on-a-Chip (SoC)

Assumed-Immutable Data is Stored in Writable Memory

Binding to an Unrestricted IP Address

Improper Isolation of Shared Resources in Network On Chip (NoC)

Use of Externally-Controlled Format String

Exposure of Sensitive Information to an Unauthorized Actor

Passing Mutable Objects to an Untrusted Method

Returning a Mutable Object to an Untrusted Caller

Further reading

Don't Let Security
Weigh You Down.

Use of Inner Class Containing Sensitive Data

What is CWE-492?

Real-world CVEs caused by CWE-492

Step-by-step attacker path

Vulnerable Java

Secure Java

How to prevent CWE-492

How to detect CWE-492

Plexicus auto-detects CWE-492 and opens a fix PR in under 60 seconds.

Frequently asked questions

Weaknesses related to CWE-492

Exposure of Resource to Wrong Sphere

Improper Isolation of Shared Resources on System-on-a-Chip (SoC)

Assumed-Immutable Data is Stored in Writable Memory

Binding to an Unrestricted IP Address

Improper Isolation of Shared Resources in Network On Chip (NoC)

Use of Externally-Controlled Format String

Exposure of Sensitive Information to an Unauthorized Actor

Passing Mutable Objects to an Untrusted Method

Returning a Mutable Object to an Untrusted Caller

Further reading

Don't Let SecurityWeigh You Down.

Don't Let Security
Weigh You Down.