Deployment of Wrong Handler

Incomplete Base
Structure: Simple
Description

This vulnerability occurs when a system incorrectly assigns or routes an object to the wrong processing component.

Extended Description

Deploying the wrong handler is a misconfiguration or logic flaw where an application sends data or a request to an unintended processing module. For instance, this could involve mistakenly routing a request for a JSP file's source code to a servlet designed to display it, rather than to the component that executes it. Such incorrect routing often bypasses the intended security controls and business logic, exposing the underlying system to unintended behavior. This issue frequently stems from flawed type-determination logic, where the system automatically infers how to handle an object, overriding an explicitly declared type. Developers encounter this when trust is placed in dynamic dispatch mechanisms, file upload handlers, or content-type resolvers that make incorrect assumptions. The core risk is that the wrong handler processes sensitive data or commands, potentially leading to information disclosure, code execution, or system manipulation.

Common Consequences 1
Scope: IntegrityOther

Impact: Varies by ContextUnexpected State

Potential Mitigations 2
Phase: Architecture and Design
Perform a type check before interpreting an object.
Phase: Architecture and Design
Reject any inconsistent types, such as a file with a .GIF extension that appears to consist of PHP code.
Observed Examples 4
CVE-2001-0004Source code disclosure via manipulated file extension that causes parsing by wrong DLL.
CVE-2002-0025Web browser does not properly handle the Content-Type header field, causing a different application to process the document.
CVE-2000-1052Source code disclosure by directly invoking a servlet.
CVE-2002-1742Arbitrary Perl functions can be loaded by calling a non-existent function that activates a handler.
References 1
The Art of Software Security Assessment
Mark Dowd, John McDonald, and Justin Schuh
Addison Wesley
2006
ID: REF-62
Applicable Platforms
Languages:
Not Language-Specific : Undetermined
Modes of Introduction
Implementation
Taxonomy Mapping
  • PLOVER