Difference between revisions of "Path Manipulation"

From OWASP
Jump to: navigation, search
(Still think it is an attack.)
(4 intermediate revisions by one user not shown)
Line 1: Line 1:
 
{{Template:Attack}}
 
{{Template:Attack}}
{{Template:Fortify}}
 
 
==Abstract==
 
 
Allowing user input to control paths used in filesystem operations may enable an attacker to access or modify otherwise protected system resources.
 
  
 
==Description==
 
==Description==
Line 12: Line 7:
 
# An attacker can specify a path used in an operation on the filesystem.  
 
# An attacker can specify a path used in an operation on the filesystem.  
 
# By specifying the resource, the attacker gains a capability that would not otherwise be permitted. For example, the program may give the attacker the ability to overwrite the specified file or run with a configuration controlled by the attacker.  
 
# By specifying the resource, the attacker gains a capability that would not otherwise be permitted. For example, the program may give the attacker the ability to overwrite the specified file or run with a configuration controlled by the attacker.  
 +
 +
Allowing user input to control paths used in filesystem operations may enable an attacker to access or modify  protected system resources.
 +
 +
== Severity ==
 +
 +
Medium to High
 +
 +
== Likelihood of exploitation ==
 +
 +
High to Very High
  
 
==Examples ==
 
==Examples ==
Line 37: Line 42:
  
 
==Related Threats==
 
==Related Threats==
 +
 +
[[:Category:Information Disclosure]]
  
 
==Related Attacks==
 
==Related Attacks==
 +
*[[Resource Injection]]
 +
*[[Relative Path Traversal]]
  
 
==Related Vulnerabilities==
 
==Related Vulnerabilities==
Line 46: Line 55:
 
[[:Category:Input Validation]]
 
[[:Category:Input Validation]]
  
==Categories==
+
==Credit==
 +
{{Template:Fortify}}
 +
 
 
[[Category:Injection Attack]]
 
[[Category:Injection Attack]]
[[Category:File System]]
+
 
[[Category:Implementation]]
+
[[Category:Attack]]
[[Category:Java]]
+
[[Category:Code Snippet]]
+

Revision as of 11:32, 5 November 2007

This is an Attack. To view all attacks, please see the Attack Category page.


Description

Path manipulation errors occur when the following two conditions are met:

  1. An attacker can specify a path used in an operation on the filesystem.
  2. By specifying the resource, the attacker gains a capability that would not otherwise be permitted. For example, the program may give the attacker the ability to overwrite the specified file or run with a configuration controlled by the attacker.

Allowing user input to control paths used in filesystem operations may enable an attacker to access or modify protected system resources.

Severity

Medium to High

Likelihood of exploitation

High to Very High

Examples

Example 1

The following code uses input from an HTTP request to create a file name. The programmer has not considered the possibility that an attacker could provide a file name such as "../../tomcat/conf/server.xml", which causes the application to delete one of its own configuration files.

	String rName = request.getParameter("reportName");
	File rFile = new File("/usr/local/apfr/reports/" + rName);
	...
	rFile.delete();

Example 2

The following code uses input from a configuration file to determine which file to open and echo back to the user. If the program runs with privileges and malicious users can change the configuration file, they can use the program to read any file on the system that ends with the extension .txt.

	fis = new FileInputStream(cfg.getProperty("sub")+".txt");
	amt = fis.read(arr);
	out.println(arr);

Related Threats

Category:Information Disclosure

Related Attacks

Related Vulnerabilities

Category:Input Validation Vulnerability

Related Countermeasures

Category:Input Validation

Credit

This article includes content generously donated to OWASP by Fortify.JPG.