Improper Handling of Syntactically Invalid Structure |
Weakness ID: 228 (Weakness Class) | Status: Incomplete |
Description Summary
Nature | Type | ID | Name | View(s) this relationship pertains to![]() |
---|---|---|---|---|
ChildOf | ![]() | 19 | Data Handling | Development Concepts (primary)699 |
ChildOf | ![]() | 137 | Representation Errors | Development Concepts699 |
ChildOf | ![]() | 703 | Failure to Handle Exceptional Conditions | Research Concepts1000 |
ChildOf | ![]() | 707 | Improper Enforcement of Message or Data Structure | Research Concepts (primary)1000 |
ChildOf | ![]() | 728 | OWASP Top Ten 2004 Category A7 - Improper Error Handling | Weaknesses in OWASP Top Ten (2004) (primary)711 |
ParentOf | ![]() | 229 | Improper Handling of Values | Development Concepts (primary)699 Research Concepts (primary)1000 |
ParentOf | ![]() | 233 | Parameter Problems | Development Concepts (primary)699 Research Concepts (primary)1000 |
ParentOf | ![]() | 237 | Improper Handling of Structural Elements | Development Concepts (primary)699 Research Concepts (primary)1000 |
ParentOf | ![]() | 241 | Improper Handling of Unexpected Data Type | Development Concepts (primary)699 Research Concepts (primary)1000 |
Mapped Taxonomy Name | Node ID | Fit | Mapped Node Name |
---|---|---|---|
PLOVER | Structure and Validity Problems | ||
OWASP Top Ten 2004 | A7 | CWE More Specific | Improper Error Handling |
This entry needs more investigation. Public vulnerability research generally focuses on the manipulations that generate invalid structure, instead of the weaknesses that are exploited by those manipulations. For example, a common attack involves making a request that omits a required field, which can trigger a crash in some cases. The crash could be due to a named chain such as CWE-690 (Unchecked Return Value to NULL Pointer Dereference), but public reports rarely cover this aspect of a vulnerability. |
The validity of input could be roughly classified along "syntactic", "semantic", and "lexical" dimensions. If the specification requires that an input value should be delimited with the "[" and "]" square brackets, then any input that does not follow this specification would be syntactically invalid. If the input between the brackets is expected to be a number, but the letters "aaa" are provided, then the input is syntactically invalid. If the input is a number and enclosed in brackets, but the number is outside of the allowable range, then it is semantically invalid. The inter-relationships between these properties - and their associated weaknesses- need further exploration. |
Submissions | ||||
---|---|---|---|---|
Submission Date | Submitter | Organization | Source | |
PLOVER | Externally Mined | |||
Modifications | ||||
Modification Date | Modifier | Organization | Source | |
2008-07-01 | Eric Dalci | Cigital | External | |
updated Time of Introduction | ||||
2008-09-08 | CWE Content Team | MITRE | Internal | |
updated Description, Maintenance Notes, Name, Relationships, Relevant Properties, Taxonomy Mappings | ||||
2009-03-10 | CWE Content Team | MITRE | Internal | |
updated Description, Name | ||||
Previous Entry Names | ||||
Change Date | Previous Entry Name | |||
2008-09-09 | Structure and Validity Problems | |||
2009-03-10 | Failure to Handle Syntactically Invalid Structure | |||