Improper Handling of Apple HFS+ Alternate Data Stream Path
Incomplete Variant
Structure: Simple
Description
The product does not properly handle special paths that may identify the data or resource fork of a file on the HFS+ file system.
If the product chooses actions to take based on the file name, then if an attacker provides the data or resource fork, the product may take unexpected actions. Further, if the product intends to restrict access to a file, then an attacker might still be able to bypass intended access restrictions by requesting the data or resource fork for that file.
Common Consequences 1
Scope: ConfidentialityIntegrity
Impact: Read Files or DirectoriesModify Files or Directories
Demonstrative Examples 1
A web server that interprets FILE.cgi as processing instructions could disclose the source code for FILE.cgi by requesting FILE.cgi/..namedfork/data. This might occur because the web server invokes the default handler which may return the contents of the file.
Observed Examples 1
CVE-2004-1084Server allows remote attackers to read files and resource fork content via HTTP requests to certain special file names related to multiple data streams in HFS+.
References 1
NetSec Security Advisory: Multiple Vulnerabilities Resulting From Use Of Apple OSX HFS+
NetSec
BugTraq
16-02-2005
https://seclists.org/bugtraq/2005/Feb/309(2023-04-07)
ID: REF-578
Applicable Platforms
Languages:
Not Language-Specific : Undetermined
Modes of Introduction
Implementation
Functional Areas
- File Processing
Affected Resources
- File or Directory
Related Weaknesses
Notes
TheoreticalThis and similar problems exist because the same resource can have multiple identifiers that dictate which behavior can be performed on the resource.
Research GapUnder-studied