387
Nature Type ID Name Page
MemberOf 990 SFP Secondary Cluster: Tainted Input to Command 888 2413
MemberOf 1407 Comprehensive Categorization: Improper Neutralization 1400 2532
Notes
Relationship
Depending on the language and syntax being used, this could be the same as the record
delimiter (CWE-143).
Taxonomy Mappings
Mapped Taxonomy Name Node ID Fit Mapped Node Name
PLOVER Section Delimiter
Software Fault Patterns SFP24 Tainted input to command
References
[REF-62]Mark Dowd, John McDonald and Justin Schuh. "The Art of Software Security
Assessment". 1st Edition. 2006. Addison Wesley.
CWE-146: Improper Neutralization of Expression/Command Delimiters
Weakness ID : 146
Structure : Simple
Abstraction : Variant
Description
The product receives input from an upstream component, but it does not neutralize or incorrectly
neutralizes special elements that could be interpreted as expression or command delimiters when
they are sent to a downstream component.
Extended Description
As data is parsed, an injected/absent/malformed delimiter may cause the process to take
unexpected actions.
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 140 Improper Neutralization of Delimiters 376
Applicable Platforms
Language : Not Language-Specific (Prevalence = Undetermined)
Common Consequences
Scope Impact Likelihood
Confidentiality
Integrity
Availability
Other
Execute Unauthorized Code or Commands
Alter Execution Logic
Potential Mitigations
CWE Version 4.14
CWE-146: Improper Neutralization of Expression/Command Delimiters
CWE-146: Improper Neutralization of Expression/Command Delimiters