Only Filtering Special Elements at a Specified Location |
Weakness ID: 795 (Weakness Base) | Status: Incomplete |
Description Summary
Extended Description
A filter might only account for instances of special elements when they occur
1) relative to a marker (e.g. "at the beginning/end of string; the second argument"), or
2) at an absolute position (e.g. "byte number 10").
This may leave special elements in the data that did not match the filter position, but still may be dangerous.
Example 1
The following code takes untrusted input and uses a regular expression to filter a "../" element located at the beginning of the input string. It then appends this result to the /home/user/ directory and attempts to read the file in the final resulting path.
Since the regular expression is only looking for an instance of "../" at the beginning of the string, it only removes the first "../" element. So an input value such as:
will have the first "../" stripped, resulting in:
This value is then concatenated with the /home/user/ directory:
which causes the /etc/passwd file to be retrieved once the operating system has resolved the ../ sequences in the pathname. This leads to relative path traversal (CWE-22).
Nature | Type | ID | Name | View(s) this relationship pertains to![]() |
---|---|---|---|---|
ChildOf | ![]() | 791 | Incomplete Filtering of Special Elements | Research Concepts (primary)1000 |
ParentOf | ![]() | 796 | Only Filtering Special Elements Relative to a Marker | Research Concepts (primary)1000 |
ParentOf | ![]() | 797 | Only Filtering Special Elements at an Absolute Position | Research Concepts (primary)1000 |