Path Equivalence: 'file name' (Internal Whitespace)
Incomplete Variant
Structure: Simple
Description
The product accepts path input in the form of internal space ('file(SPACE)name') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
Common Consequences 1
Scope: ConfidentialityIntegrity
Impact: Read Files or DirectoriesModify Files or Directories
Observed Examples 2
CVE-2000-0293Filenames with spaces allow arbitrary file deletion when the product does not properly quote them; some overlap with path traversal.
CVE-2001-1567"+" characters in query string converted to spaces before sensitive file/extension (internal space), leading to bypass of access restrictions to the file.
Applicable Platforms
Languages:
Not Language-Specific : Undetermined
Modes of Introduction
Implementation
Functional Areas
- File Processing
Affected Resources
- File or Directory
Related Weaknesses
Taxonomy Mapping
- PLOVER
- OWASP Top Ten 2004
- Software Fault Patterns
Notes
RelationshipThis weakness is likely to overlap quoting problems, e.g. the "Program Files" unquoted search path (Unquoted Search Path or Element). It also could be an equivalence issue if filtering removes all extraneous spaces.
RelationshipWhitespace can be a factor in other weaknesses not directly related to equivalence. It can also be used to spoof icons or hide files with dangerous names (see icon manipulation and visual truncation in User Interface (UI) Misrepresentation of Critical Information).