425
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 722 OWASP Top Ten 2004 Category A1 - Unvalidated Input 711 2334
MemberOf 992 SFP Secondary Cluster: Faulty Input Transformation 888 2416
MemberOf 1407 Comprehensive Categorization: Improper Neutralization 1400 2532
Taxonomy Mappings
Mapped Taxonomy Name Node ID Fit Mapped Node Name
PLOVER Missing Special Element
CWE-167: Improper Handling of Additional Special Element
Weakness ID : 167
Structure : Simple
Abstraction : Base
Description
The product receives input from an upstream component, but it does not handle or incorrectly
handles when an additional unexpected special element is provided.
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 228 Improper Handling of Syntactically Invalid Structure 568
ChildOf 159 Improper Handling of Invalid Use of Special Elements 411
Relevant to the view "Software Development" (CWE-699)
Nature Type ID Name Page
MemberOf 19 Data Processing Errors 2309
Applicable Platforms
Language : Not Language-Specific (Prevalence = Undetermined)
Common Consequences
Scope Impact Likelihood
Integrity Unexpected State
Potential Mitigations
Developers should anticipate that extra special elements will be injected in the input vectors of
their product. Use an appropriate combination of denylists and allowlists to ensure only valid,
expected and appropriate input is processed by the system.
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
CWE Version 4.14
CWE-168: Improper Handling of Inconsistent Special Elements
CWE-168: Improper Handling of Inconsistent Special Elements