Comparison of Classes by Name

Opis

The product compares classes by name, which can cause it to use the wrong class when multiple classes can have the same name.

If the decision to trust the methods and data of an object is based on the name of a class, it is possible for malicious users to send objects of the same name as trusted classes and thereby gain the trust afforded to known classes and types.

Skutki

• Integrity, Confidentiality, Availability

  Execute Unauthorized Code or Commands

  If a product relies solely on the name of an object to determine identity, it may execute the incorrect or unintended code.

Zapobieganie

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

Słabość nadrzędna

• CWE-1025 Comparison Using Wrong Factors

Kiedy powstaje

• Implementation

Dotyczy

Java

Źródła

1. Seven Pernicious Kingdoms: A Taxonomy of Software Security Errors — Katrina Tsipenyuk, Brian Chess, Gary McGraw, NIST, 2005
2. The CLASP Application Security Process — Secure Software, Inc., 2005