CWE-48
Weakness AllowedPath Equivalence: 'file name' (Internal Whitespace)
Abstraction: Variant · Status: Incomplete
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.
Mapping guidance
This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
Modes of introduction
Notes
Relationship
This weakness is likely to overlap quoting problems, e.g. the "Program Files" unquoted search path (CWE-428). It also could be an equivalence issue if filtering removes all extraneous spaces.
Relationship
Whitespace 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 CWE-451).
Content history
updated Time_of_Introduction
updated Relationships, Other_Notes, Taxonomy_Mappings
updated Common_Consequences
updated Relationships
updated Potential_Mitigations
updated Applicable_Platforms, Other_Notes, Relationship_Notes
updated Relationships, Taxonomy_Mappings
updated Relationships
updated Description
updated Relationships
updated Mapping_Notes
updated Affected_Resources, Functional_Areas
updated Weakness_Ordinalities
0 vulnerabilities reference this CWE, most recent first.
No vulnerabilities reference this CWE.
No mitigation information available for this CWE.
No CAPEC attack patterns related to this CWE.