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.)
CWE-486 Variante Borrador
Comparison of Classes by Name
This vulnerability occurs when an application determines an object's trustworthiness or behavior solely by checking its class name. Since multiple classes can share identical names across different…
Definición
What is CWE-486?
This vulnerability occurs when an application determines an object's trustworthiness or behavior solely by checking its class name. Since multiple classes can share identical names across different packages or classloaders, this comparison can lead to using the wrong, potentially malicious, class.
Relying on class name strings for security decisions is inherently risky. Attackers can craft classes with names identical to your trusted ones, tricking your application into granting them unauthorized privileges or executing unintended code paths. This is especially problematic in environments with multiple classloaders, like application servers, where the same fully-qualified name can point to completely different implementations.
Detecting these logical flaws manually is challenging, as they depend on runtime context. While SAST tools can flag dangerous comparison patterns, Plexicus uses AI to not only identify the risk but also suggest specific, secure refactoring—such as using direct class object comparisons or verifying the classloader—saving significant manual review time and preventing impersonation attacks.
Impacto en el mundo real
Real-world CVEs caused by CWE-486
Todavía no hay CVEs públicos enlazados a esta CWE en el catálogo de MITRE.
Cómo lo explotan los atacantes
Ruta del atacante paso a paso
- 1
In this example, the expression in the if statement compares the class of the inputClass object to a trusted class by comparing the class names.
- 2
However, multiple classes can have the same name therefore comparing an object's class by name can allow untrusted classes of the same name as the trusted class to be use to execute unintended or incorrect code. To compare the class of an object to the intended class the getClass() method and the comparison operator "==" should be used to ensure the correct trusted class is used, as shown in the following example.
- 3
In this example, the Java class, TrustedClass, overrides the equals method of the parent class Object to determine equivalence of objects of the class. The overridden equals method first determines if the object, obj, is the same class as the TrustedClass object and then compares the object's fields to determine if the objects are equivalent.
- 4
However, the equals method compares the class names of the object, obj, and the TrustedClass object to determine if they are the same class. As with the previous example using the name of the class to compare the class of objects can lead to the execution of unintended or incorrect code if the object passed to the equals method is of another class with the same name. To compare the class of an object to the intended class, the getClass() method and the comparison operator "==" should be used to ensure the correct trusted class is used, as shown in the following example.
Ejemplo de código vulnerable
Vulnerable Java
In this example, the expression in the if statement compares the class of the inputClass object to a trusted class by comparing the class names.
if (inputClass.getClass().getName().equals("TrustedClassName")) {
```
// Do something assuming you trust inputClass*
*// ...*
} Ejemplo de código seguro
Secure Java
However, multiple classes can have the same name therefore comparing an object's class by name can allow untrusted classes of the same name as the trusted class to be use to execute unintended or incorrect code. To compare the class of an object to the intended class the getClass() method and the comparison operator "==" should be used to ensure the correct trusted class is used, as shown in the following example.
if (inputClass.getClass() == TrustedClass.class) {
```
// Do something assuming you trust inputClass*
*// ...*
} What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Lista de prevención
How to prevent CWE-486
- Implementation Use class equivalency to determine type. Rather than use the class name to determine if an object is of a given type, use the getClass() method, and == operator.
Señales de detección
How to detect CWE-486
CWE-486
Don't catalog this weakness. Prove it's reachable.
Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.
Preguntas frecuentes ¿Qué es CWE-486?
¿Qué gravedad tiene CWE-486?
¿Qué lenguajes o plataformas se ven afectados por CWE-486?
¿Cómo puedo prevenir CWE-486?
¿Cómo detecta y corrige Plexicus CWE-486?
¿Dónde puedo aprender más sobre CWE-486?
Frequently asked questions
¿Qué es CWE-486?
This vulnerability occurs when an application determines an object's trustworthiness or behavior solely by checking its class name. Since multiple classes can share identical names across different packages or classloaders, this comparison can lead to using the wrong, potentially malicious, class.
¿Qué gravedad tiene CWE-486?
MITRE califica la probabilidad de explotación como Alta — esta debilidad se explota activamente en la práctica y debe priorizarse para su remediación.
¿Qué lenguajes o plataformas se ven afectados por CWE-486?
MITRE lists the following affected platforms: Java.
¿Cómo puedo prevenir CWE-486?
Use class equivalency to determine type. Rather than use the class name to determine if an object is of a given type, use the getClass() method, and == operator.
¿Cómo detecta y corrige Plexicus CWE-486?
El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-486 en cada commit. Cuando hay coincidencia, nuestro agente Codex Remedium abre un PR de corrección con el código corregido, las pruebas y un resumen de una línea para el revisor.
¿Dónde puedo aprender más sobre CWE-486?
MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/486.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.
Debilidades relacionadas
Weaknesses related to CWE-486
CWE-1025 Padre
Comparison Using Wrong Factors
This weakness occurs when a program compares two items but checks the wrong properties or attributes. This flawed comparison leads to…
CWE-595 Hermano
Comparison of Object References Instead of Object Contents
This vulnerability occurs when code incorrectly checks if two object references point to the same memory location, rather than comparing…
Recursos
Further reading
- MITRE — CWE-486 oficial https://cwe.mitre.org/data/definitions/486.html
- Seven Pernicious Kingdoms: A Taxonomy of Software Security Errors https://samate.nist.gov/SSATTM_Content/papers/Seven%20Pernicious%20Kingdoms%20-%20Taxonomy%20of%20Sw%20Security%20Errors%20-%20Tsipenyuk%20-%20Chess%20-%20McGraw.pdf
- The CLASP Application Security Process https://cwe.mitre.org/documents/sources/TheCLASPApplicationSecurityProcess.pdf
¿Listo para validar lo que importa?
Listo para validar lo que importa.
Plexicus es Proof-Driven AppSec: hallazgos validados, comprensión contextual y remediación revisada — anclada en evidencia, acotada contigo.