1042
CWE-430: Deployment of Wrong Handler
Weakness ID : 430
Structure : Simple
Abstraction : Base
Description
The wrong "handler" is assigned to process an object.
Extended Description
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.
Relationships
The table(s) below shows the weaknesses and high level categories that are related to this
weakness. These relationships are defined as ChildOf, ParentOf, MemberOr and give insight to
similar items that may exist at higher and lower levels of abstraction. In addition, relationships such
as PeerOf and CanAlsoBe are defined to show similar weaknesses that may want to be explored.
Relevant to the view "Research Concepts" (CWE-1000)
Nature Type ID Name Page
ChildOf 691 Insufficient Control Flow Management 1517
PeerOf 434 Unrestricted Upload of File with Dangerous Type 1048
PeerOf 434 Unrestricted Upload of File with Dangerous Type 1048
CanPrecede 433 Unparsed Raw Web Content Delivery 1046
Relevant to the view "Software Development" (CWE-699)
Nature Type ID Name Page
MemberOf 429 Handler Errors 2326
Weakness Ordinalities
Resultant : This weakness is usually resultant from other weaknesses.
Applicable Platforms
Language : Not Language-Specific (Prevalence = Undetermined)
Common Consequences
Scope Impact Likelihood
Integrity
Other
Varies by Context
Unexpected State
Potential Mitigations
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
Reference Description
CVE-2001-0004 Source code disclosure via manipulated file extension that causes parsing by
wrong DLL.
https://www.cve.org/CVERecord?id=CVE-2001-0004
CWE Version 4.14
CWE-431: Missing Handler
CWE-431: Missing Handler