结构: Simple
Abstraction: Variant
状态: Incomplete
被利用可能性: unkown
The software does not properly handle special paths that may identify the data or resource fork of a file on the HFS+ file system.
If the software chooses actions to take based on the file name, then if an attacker provides the data or resource fork, the software may take unexpected actions. Further, if the software 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.
cwe_Nature: ChildOf cwe_CWE_ID: 66 cwe_View_ID: 1000 cwe_Ordinal: Primary
cwe_Nature: ChildOf cwe_CWE_ID: 66 cwe_View_ID: 699 cwe_Ordinal: Primary
Language: {'cwe_Class': 'Language-Independent', 'cwe_Prevalence': 'Undetermined'}
Operating_System: {'cwe_Class': 'macOS', 'cwe_Prevalence': 'Undetermined'}
范围 | 影响 | 注释 |
---|---|---|
['Confidentiality', 'Integrity'] | ['Read Files or Directories', 'Modify Files or Directories'] |
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.
标识 | 说明 | 链接 |
---|---|---|
Theoretical This and similar problems exist because the same resource can have multiple identifiers that dictate which behavior can be performed on the resource. Research Gap Under-studied