69
Taxonomy Mappings
Mapped Taxonomy Name Node ID Fit Mapped Node Name
PLOVER '...' (triple dot)
Software Fault Patterns SFP16 Path Traversal
CWE-33: Path Traversal: '....' (Multiple Dot)
Weakness ID : 33
Structure : Simple
Abstraction : Variant
Description
The product uses external input to construct a pathname that should be within a restricted
directory, but it does not properly neutralize '....' (multiple dot) sequences that can resolve to a
location that is outside of that directory.
Extended Description
This allows attackers to traverse the file system to access files or directories that are outside of the
restricted directory.
The '....' manipulation is useful for bypassing some path traversal protection schemes. On some
Windows systems, it is equivalent to "..\..\.." and might bypass checks that assume only two dots
are valid. Incomplete filtering, such as removal of "./" sequences, can ultimately produce valid ".."
sequences due to a collapse into unsafe value (CWE-182).
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 23 Relative Path Traversal 46
CanFollow 182 Collapse of Data into Unsafe Value 455
Applicable Platforms
Language : Not Language-Specific (Prevalence = Undetermined)
Common Consequences
Scope Impact Likelihood
Confidentiality
Integrity
Read Files or Directories
Modify Files or Directories
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
CWE Version 4.14
CWE-33: Path Traversal: '....' (Multiple Dot)
CWE-33: Path Traversal: '....' (Multiple Dot)