422
Nature Type ID Name Page
MemberOf 1407 Comprehensive Categorization: Improper Neutralization 1400 2532
Taxonomy Mappings
Mapped Taxonomy Name Node ID Fit Mapped Node Name
PLOVER Internal Special Element
Software Fault Patterns SFP24 Tainted input to command
CWE-165: Improper Neutralization of Multiple Internal Special Elements
Weakness ID : 165
Structure : Simple
Abstraction : Variant
Description
The product receives input from an upstream component, but it does not neutralize or incorrectly
neutralizes multiple internal special elements that could be interpreted in unexpected ways when
they are sent to a downstream component.
Extended Description
As data is parsed, improperly handled multiple internal special elements may cause the process to
take unexpected actions that result in an attack.
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 164 Improper Neutralization of Internal Special Elements 420
ParentOf 45 Path Equivalence: 'file...name' (Multiple Internal Dot) 95
ParentOf 53 Path Equivalence: '\multiple\\internal\backslash' 104
Applicable Platforms
Language : Not Language-Specific (Prevalence = Undetermined)
Common Consequences
Scope Impact Likelihood
Integrity Unexpected State
Potential Mitigations
Developers should anticipate that multiple internal special elements will be injected/removed/
manipulated 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
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
CWE Version 4.14
CWE-166: Improper Handling of Missing Special Element
CWE-166: Improper Handling of Missing Special Element