CWE-486 Variante Brouillon High likelihood

Comparison of Classes by Name

Définition

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.

Impact réel

Real-world CVEs caused by CWE-486

Aucune référence CVE publique n'est liée à ce CWE dans le catalogue MITRE pour le moment.

Comment les attaquants l'exploitent

Parcours de l'attaquant étape par étape

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.

Exemple de code vulnérable

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.

Vulnérable Java

if (inputClass.getClass().getName().equals("TrustedClassName")) {
```
// Do something assuming you trust inputClass* 
  		
  		
  		 *// ...* 
  		}

Exemple de code sécurisé

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.

Sécurisé Java

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.

Liste de contrôle de prévention

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.

Signaux de détection

How to detect CWE-486

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.)

Correction automatique Plexicus

Plexicus détecte automatiquement CWE-486 et ouvre une PR de correction en moins de 60 secondes.

Codex Remedium analyse chaque commit, identifie cette faiblesse précise et livre une pull request prête à être relue avec le correctif. Pas de tickets. Pas de transferts.

Obtenir une démo Essayer Plexicus gratuitement

Questions fréquentes

Frequently asked questions

Qu'est-ce que CWE-486 ?

Quelle est la gravité de CWE-486 ?

MITRE évalue la probabilité d'exploitation comme Élevée — cette faiblesse est activement exploitée et doit être priorisée pour la remédiation.

Quels langages ou plateformes sont affectés par CWE-486 ?

MITRE lists the following affected platforms: Java.

Comment puis-je prévenir 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.

Comment Plexicus détecte et corrige CWE-486 ?

Le moteur SAST de Plexicus reconnaît la signature de flux de données de CWE-486 à chaque commit. Lorsqu'une correspondance est trouvée, notre agent Codex Remedium ouvre une PR de correction avec le code corrigé, les tests et un résumé d'une ligne pour le relecteur.

Où puis-je en savoir plus sur CWE-486 ?

MITRE publie la définition canonique à https://cwe.mitre.org/data/definitions/486.html. Vous pouvez également consulter la documentation OWASP et NIST pour des conseils adjacents.

Faiblesses associées

Weaknesses related to CWE-486

CWE-1025 Parent

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 Frère

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…

Ressources

Arrêtez de payer par développeur.
Commencez à fermer la boucle.

Plexicus est l'ASPM natif IA qui scanne, filtre, corrige, penteste et explique — de façon autonome. Développeurs illimités, dépôts illimités, actions IA à usage équitable. Vrai niveau gratuit, €269/mo annuel quand vous êtes prêt.

Commencer gratuitement Réserver une démo