Misinterpretation of Input
Incomplete Base
Structure: Simple
Description
The product misinterprets an input, whether from an attacker or another product, in a security-relevant fashion.
Common Consequences 1
Scope: Integrity
Impact: Unexpected State
Detection Methods 1
FuzzingHigh
Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.Observed Examples 2
CVE-2005-2225Product sees dangerous file extension in free text of a group discussion, disconnects all users.
CVE-2001-0003Product does not correctly import and process security settings from another product.
Applicable Platforms
Languages:
Not Language-Specific : Undetermined
Modes of Introduction
Architecture and Design
Implementation
Related Weaknesses
ChildOf:
Interpretation Conflict (CWE-436)
Taxonomy Mapping
- PLOVER
Notes
Research GapThis concept needs further study. It is likely a factor in several weaknesses, possibly resultant as well. Overlaps Multiple Interpretation Errors (MIE).