Deployment of Wrong Handler

Opis

The wrong "handler" is assigned to process an object.

An example of deploying the wrong handler would be calling a servlet to reveal source code of a .JSP file, or automatically "determining" type of the object even if it is contradictory to an explicitly specified type.

Skutki

• Integrity, Other

  Varies by Context; Unexpected State

Zapobieganie

• Architecture and Design

  Perform a type check before interpreting an object.

• Architecture and Design

  Reject any inconsistent types, such as a file with a .GIF extension that appears to consist of PHP code.

Przykłady podatności

• CVE-2001-0004 Source code disclosure via manipulated file extension that causes parsing by wrong DLL.
• CVE-2002-0025 Web browser does not properly handle the Content-Type header field, causing a different application to process the document.
• CVE-2000-1052 Source code disclosure by directly invoking a servlet.
• CVE-2002-1742 Arbitrary Perl functions can be loaded by calling a non-existent function that activates a handler.

Słabość nadrzędna

• CWE-691 Insufficient Control Flow Management

Może prowadzić do

• CWE-433 Unparsed Raw Web Content Delivery

Pokrewna

• CWE-434 Unrestricted Upload of File with Dangerous Type

Kiedy powstaje

• Implementation

Dotyczy

Not Language-Specific, Not Technology-Specific

Źródła

1. The Art of Software Security Assessment — Mark Dowd, John McDonald, Justin Schuh, Chapter 3, "File Handlers", Page 74, Addison Wesley, 2006