CWE-430
Deployment of Wrong Handler
Incomplete
2006-07-19 00:00 +00:00
2023-06-29 00:00 +00:00
Alerte pour un CWE
Stay informed of any changes for a specific CWE.
Deployment of Wrong Handler
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.
Informations
Modes Of Introduction
ImplementationApplicable Platforms
Language
Class: Not Language-Specific (Undetermined)Common Consequences
| Scope | Impact | Likelihood |
|---|---|---|
| Integrity Other | Varies by Context, Unexpected State |
Observed Examples
| Reference | Description |
|---|---|
| Source code disclosure via manipulated file extension that causes parsing by wrong DLL. | |
| Web browser does not properly handle the Content-Type header field, causing a different application to process the document. | |
| Source code disclosure by directly invoking a servlet. | |
| Arbitrary Perl functions can be loaded by calling a non-existent function that activates a handler. |
Potential Mitigations
Phases : Architecture and DesignPerform a type check before interpreting an object.
Phases : Architecture and Design
Reject any inconsistent types, such as a file with a .GIF extension that appears to consist of PHP code.
Vulnerability Mapping Notes
Rationale : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.Comments : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
Related Attack Patterns
| CAPEC-ID | Attack Pattern Name |
|---|---|
| CAPEC-11 | Cause Web Server Misclassification An attack of this type exploits a Web server's decision to take action based on filename or file extension. Because different file types are handled by different server processes, misclassification may force the Web server to take unexpected action, or expected actions in an unexpected sequence. This may cause the server to exhaust resources, supply debug or system data to the attacker, or bind an attacker to a remote process. |
References
REF-62
The Art of Software Security AssessmentMark Dowd, John McDonald, Justin Schuh.
Submission
| Name | Organization | Date | Date Release | Version |
|---|---|---|---|---|
| PLOVER | Draft 3 |
Modifications
| Name | Organization | Date | Comment |
|---|---|---|---|
| Eric Dalci | Cigital | updated Potential_Mitigations, Time_of_Introduction | |
| CWE Content Team | MITRE | updated Relationships, Other_Notes, Taxonomy_Mappings | |
| CWE Content Team | MITRE | updated Description | |
| CWE Content Team | MITRE | updated Other_Notes, Weakness_Ordinalities | |
| CWE Content Team | MITRE | updated Common_Consequences | |
| CWE Content Team | MITRE | updated Common_Consequences | |
| CWE Content Team | MITRE | updated References, Relationships | |
| CWE Content Team | MITRE | updated Potential_Mitigations | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Applicable_Platforms | |
| CWE Content Team | MITRE | updated Related_Attack_Patterns | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Mapping_Notes |
2024©
tesweb SA
