Directory Restriction Error - Revision history

Imifos at 12:35, 22 January 2016

2016-01-22T12:35:55Z

Imifos at 12:42, 2 December 2015

2015-12-02T12:42:31Z

KirstenS: /* Examples */

2009-02-21T18:08:44Z

‎Examples

KirstenS: /* Examples */

2009-02-21T18:07:01Z

‎Examples

KirstenS at 00:36, 21 February 2009

2009-02-21T00:36:02Z

KirstenS at 02:14, 18 February 2009

2009-02-18T02:14:03Z

KirstenS at 12:48, 30 October 2008

2008-10-30T12:48:23Z

KirstenS at 13:45, 13 October 2008

2008-10-13T13:45:41Z

KirstenS at 22:51, 23 September 2008

2008-09-23T22:51:09Z

KirstenS at 22:50, 23 September 2008

2008-09-23T22:50:48Z

@@ Line 1: / Line 1: @@
 {{Template:Stub}}
 {{Template:Vulnerability}}
-{{Template:Fortify}}
 Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
@@ Line 95: / Line 95: @@
 [[Category:OWASP ASDR Project]]
-[[Category:OWASP C/C++ Project]]
+[[Category:C/C++]]
 [[Category:Implementation]]
 [[Category:Code Snippet]]

@@ Line 95: / Line 95: @@
 [[Category:OWASP ASDR Project]]
-[[Category:C]]
+[[Category:OWASP C/C++ Project]]
 [[Category:Implementation]]
 [[Category:Code Snippet]]

@@ Line 15: / Line 15: @@
 == Examples ==
-Improper use of the chroot() system call may allow attackers to access files that are outside the new root directory therefore breaks the intended access control policy.
+Improper use of the chroot() system call may allow attackers to access files that are outside the new root directory, and therefore breaks the intended access control policy.
-The chroot() system call allows a process to change its perception of the root directory of the file system. After properly invoking chroot(), a process cannot access any files outside the directory tree defined by the new root directory. Such an environment is called a chroot jail and is commonly used to prevent the possibility that a processes could be subverted and used to access unauthorized files. For instance, many FTP servers run in chroot jails to prevent an attacker who discovers a new vulnerability in the server from being able to download the password file or other sensitive files on the system.
+The chroot() system call allows a process to change its perception of the root directory of the file system. After properly invoking chroot(), a process cannot access any files outside the directory tree defined by the new root directory. Such an environment is called a chroot jail, and is commonly used to prevent the possibility that a processes could be subverted and used to access unauthorized files. For instance, many FTP servers run in chroot jails to prevent an attacker who discovers a new vulnerability in the server from being able to download the password file or other sensitive files on the system.
 Improper use of chroot() may allow attackers to escape from the chroot jail. The chroot() function call does not change the process's current working directory, so relative paths may still refer to file system resources outside of the chroot jail after chroot() has been called.

@@ Line 15: / Line 15: @@
 == Examples ==
-* Improper use of the chroot() system call may allow attackers to access files that are outside the new root directory therefore breaks the intended access control policy.
+Improper use of the chroot() system call may allow attackers to access files that are outside the new root directory therefore breaks the intended access control policy.
 The chroot() system call allows a process to change its perception of the root directory of the file system. After properly invoking chroot(), a process cannot access any files outside the directory tree defined by the new root directory. Such an environment is called a chroot jail and is commonly used to prevent the possibility that a processes could be subverted and used to access unauthorized files. For instance, many FTP servers run in chroot jails to prevent an attacker who discovers a new vulnerability in the server from being able to download the password file or other sensitive files on the system.
@@ Line 33: / Line 33: @@
 This code is responsible for reading a filename from the network, opening the corresponding file on the local machine, and sending the contents over the network. This code could be used to implement the FTP GET command. The FTP server calls chroot() in its initialization routines in an attempt to prevent access to files outside of /var/ftproot. But because the server fails to change the current working directory by calling chdir("/"), an attacker could request the file "../../../../../etc/passwd" and obtain a copy of the system password file.
 ==Risk Factors==

@@ Line 2: / Line 2: @@
 {{Template:Vulnerability}}
 {{Template:Fortify}}
 Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
+[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
 ==Description==

@@ Line 3: / Line 3: @@
 {{Template:Fortify}}
-[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
+[[ASDR Table of Contents]]
 Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
 [[Category:FIXME|Stub article, needs review]]
@@ Line 111: / Line 108: @@
 [[Category:Use of Dangerous API]]
 [[Category:API Abuse]]

← Older revision		Revision as of 13:45, 13 October 2008
Line 13:		Line 13:
	__TOC__		__TOC__

		+
		+	[[Category:FIXME\|Stub article, needs review]]

	==Description==		==Description==

@@ Line 1: / Line 1: @@
 {{Template:Vulnerability}}
 {{Template:Fortify}}
-==Abstract==
+[[ASDR Table of Contents]]
 ==Description==
 The application fails to enforce the intended restricted directory access policy. By using relative paths or other path traversal attack mechanisms, an attacker can access unauthorized files outside the restricted directory.
@@ Line 32: / Line 41: @@
-Attackers try to access unauthorized files, such as password files or configuration files.
+==Risk Factors==
-==Related Attacks==
+Encoding Vulnerability
-[[Path Traversal Attacks]]
+Error Handling Vulnerability
-==Related Countermeasures==
+Input Validation Vulnerability
-[[Input Validation]]
+Logging and Auditing Vulnerability
-[[Access Control]]
+Session Management Vulnerability]]
-==Categories==
+__NOTOC__
 [[Category:C]]
 [[Category:Implementation]]
 [[Category:Code Snippet]]
 [[Category:Use of Dangerous API]]
 [[Category:API Abuse]]