Difference between revisions of "Path Manipulation"

From OWASP
Jump to: navigation, search
 
(4 intermediate revisions by one user not shown)
Line 2: Line 2:
 
<br>
 
<br>
 
[[Category:OWASP ASDR Project]]
 
[[Category:OWASP ASDR Project]]
[[ASDR Table of Contents]]__TOC__
 
  
  
==Description==
+
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
  
 +
==Description==
 
Path manipulation errors occur when the following two conditions are met:
 
Path manipulation errors occur when the following two conditions are met:
  
Line 16: Line 16:
 
==Risk Factors==
 
==Risk Factors==
 
TBD
 
TBD
[[Category:FIXME|need content here]]
 
  
 
==Examples ==
 
==Examples ==
Line 42: Line 41:
  
 
==Related [[Threat Agents]]==
 
==Related [[Threat Agents]]==
 
 
* [[:Category:Information Disclosure]]
 
* [[:Category:Information Disclosure]]
 +
[[Category:FIXME|this link doesn't exist, create category or change link?]]
  
 
==Related [[Attacks]]==
 
==Related [[Attacks]]==
*[[Resource Injection]]
+
* [[Resource Injection]]
*[[Relative Path Traversal]]
+
* [[Relative Path Traversal]]
  
 
==Related [[Vulnerabilities]]==
 
==Related [[Vulnerabilities]]==
Line 54: Line 53:
 
==Related [[Controls]]==
 
==Related [[Controls]]==
 
* [[:Category:Input Validation]]
 
* [[:Category:Input Validation]]
 +
 +
==References==
 +
TBD
  
 
==Credit==
 
==Credit==
Line 59: Line 61:
  
 
[[Category:Injection Attack]]
 
[[Category:Injection Attack]]
 
 
[[Category:Attack]]
 
[[Category:Attack]]

Latest revision as of 06:47, 23 April 2009

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




Last revision (mm/dd/yy): 04/23/2009

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.

Risk Factors

TBD

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 Threat Agents

Related Attacks

Related Vulnerabilities

Related Controls

References

TBD

Credit

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