|Name ||File System Function Injection, Content Based |
|Summary ||An attack of this type exploits the host's trust in executing remote content including binary files. The files are poisoned with a malicious payload (targeting the file systems accessible by the target software) by the attacker and may be passed through standard channels such as via email, and standard web content like PDF and multimedia files. The attacker exploits known vulnerabilities or handling routines in the target processes. Vulnerabilities of this type have been found in a wide variety of commercial applications from Microsoft Office to Adobe Acrobat and Apple Safari web browser. When the attacker knows the standard handling routines and can identify vulnerabilities and entry points they can be exploited by otherwise seemingly normal content. Once the attack is executed, the attackers' program can access relative directories such as C:\Program Files or other standard system directories to launch further attacks. In a worst case scenario, these programs are combined with other propagation logic and work as a virus. |
|Prerequisites ||The target software must consume files.
The attacker must have access to modify files that the target software will consume. |
|Solutions ||Design: Enforce principle of least privilege
Design: Validate all input for content including files. Ensure that if files and remote content must be accepted that once accepted, they are placed in a sandbox type location so that lower assurance clients cannot write up to higher assurance processes (like Web server processes for example)
Design: Execute programs with constrained privileges, so parent process does not open up further vulnerabilities. Ensure that all directories, temporary directories and files, and memory are executing with limited privileges to protect against remote execution.
Design: Proxy communication to host, so that communications are terminated at the proxy, sanitizing the requests before forwarding to server host.
Implementation: Virus scanning on host
Implementation: Host integrity monitoring for critical files, directories, and processes. The goal of host integrity monitoring is to be aware when a security issue has occurred so that incident response and other forensic activities can begin. |
|CWE ID ||Description |
|CWE-22 ||Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') |
|CWE-23 ||Relative Path Traversal |
|CWE-77 ||Improper Neutralization of Special Elements used in a Command ('Command Injection') |
|CWE-713 ||OWASP Top Ten 2007 Category A2 - Injection Flaws |
|CWE-715 ||OWASP Top Ten 2007 Category A4 - Insecure Direct Object Reference |