2140
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 20 Improper Input Validation 20
Relevant to the view "Software Development" (CWE-699)
Nature Type ID Name Page
MemberOf 1215 Data Validation Issues 2478
Applicable Platforms
Language : Not Language-Specific (Prevalence = Often)
Common Consequences
Scope Impact Likelihood
Other Varies by Context
Potential Mitigations
Phase: Implementation
Strategy = Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use
a list of acceptable inputs that strictly conform to specifications. Reject any input that does not
strictly conform to specifications, or transform it into something that does. When performing
input validation, consider all potentially relevant properties, including length, type of input, the
full range of acceptable values, missing or extra inputs, syntax, consistency across related
fields, and conformance to business rules. As an example of business rule logic, "boat" may be
syntactically valid because it only contains alphanumeric characters, but it is not valid if the input
is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for
malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if
the code's environment changes. This can give attackers enough room to bypass the intended
validation. However, denylists can be useful for detecting potential attacks or determining which
inputs are so malformed that they should be rejected outright.
Effectiveness = High
Observed Examples
Reference Description
CVE-2018-16733 product does not validate that the start block appears before the end block
https://www.cve.org/CVERecord?id=CVE-2018-16733
CVE-2006-3790 size field that is inconsistent with packet size leads to buffer over-read
https://www.cve.org/CVERecord?id=CVE-2006-3790
CVE-2008-4114 system crash with offset value that is inconsistent with packet size
https://www.cve.org/CVERecord?id=CVE-2008-4114
MemberOf Relationships
This MemberOf relationships table shows additional CWE Catgeories and Views that reference this
weakness as a member. This information is often useful in understanding where a weakness fits
within the context of external information sources.
Nature Type ID Name Page
MemberOf 1406 Comprehensive Categorization: Improper Input
Validation
1400 2531
CWE Version 4.14
CWE-1289: Improper Validation of Unsafe Equivalence in Input
CWE-1289: Improper Validation of Unsafe Equivalence in Input