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.
Potential Impact
Confidentiality, Integrity
Read Files or Directories, Modify Files or Directories
Real-World CVE Examples
| CVE ID | Description |
|---|---|
| CVE-2000-0293 | Filenames 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. |
Related Weaknesses
Taxonomy Mappings
- PLOVER: — file(SPACE)name (internal space)
- OWASP Top Ten 2004: A9 — Denial of Service
- Software Fault Patterns: SFP16 — Path Traversal
Frequently Asked Questions
What is CWE-48?
CWE-48 (Path Equivalence: 'file name' (Internal Whitespace)) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Variant-level weakness. 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...
How can CWE-48 be exploited?
Attackers can exploit CWE-48 (Path Equivalence: 'file name' (Internal Whitespace)) to read files or directories, modify files or directories. This weakness is typically introduced during the Implementation phase of software development.
How do I prevent CWE-48?
Follow secure coding practices, conduct code reviews, and use automated security testing tools (SAST/DAST) to detect this weakness early in the development lifecycle.
What is the severity of CWE-48?
CWE-48 is classified as a Variant-level weakness (Low-Medium abstraction). It has been observed in 2 real-world CVEs.