Cross-User Defacement - Revision history

MediaWiki spam cleanup: Reverting to last version not containing links to www.textacelolocna.com

2009-05-27T18:29:31Z

Reverting to last version not containing links to www.textacelolocna.com

2009-05-22T16:32:50Z

2009-04-23T11:40:51Z

2009-04-07T23:29:52Z

2009-02-17T01:54:17Z

2009-02-14T15:17:18Z

2008-09-14T01:14:32Z

2008-09-12T22:34:35Z

‎Related Attacks

2008-09-10T20:17:57Z

‎Description

2008-09-10T20:15:26Z

@@ Line 4: / Line 4: @@
 <br>
 [[Category:OWASP ASDR Project]]
 ==Description==

@@ Line 4: / Line 4: @@
 <br>
 [[Category:OWASP ASDR Project]]
 ==Description==

← Older revision		Revision as of 01:54, 17 February 2009
Line 18:		Line 18:
	==Risk Factors==		==Risk Factors==
	TBD		TBD
−	~~[[Category:FIXME\|need content here]]~~

@@ Line 4: / Line 4: @@
 <br>
 [[Category:OWASP ASDR Project]]
-[[ASDR Table of Contents]]__TOC__
+[[ASDR Table of Contents]]
 ==Description==
 An attacker can make a single request to a vulnerable server that will cause the sever to create two responses, the second of which may be misinterpreted as a response to a different request, possibly one made by another user sharing the same TCP connection with the sever. This can be accomplished by convincing the user to submit the malicious request themselves, or remotely in situations where the attacker and the user share a common TCP connection to the server, such as a shared proxy server. In the best case, an attacker can leverage this ability to convince users that the application has been hacked, causing users to lose confidence in the security of the application. In the worst case, an attacker may provide specially crafted content designed to mimic the behavior of the application but redirect private information, such as account numbers and passwords, back to the attacker.
@@ Line 26: / Line 25: @@
 to this service.
-E.g.
+Example:
 http://testsite.com/redir.php?page=http://other.testsite.com/
@@ Line 91: / Line 90: @@
 [[Category:Abuse of Functionality]]
 [[Category:Attack]]

@@ Line 72: / Line 72: @@
 ==Related [[Threat Agents]]==
-TBD
+* TBD
 ==Related [[Attacks]]==
 * [[HTTP Response Splitting]]
-*[[HTTP Response Splitting]]
+* [[Cache Poisoning]]
 ==Related [[Vulnerabilities]]==
+* [[:Category:Input Validation Vulnerability]]
 ==Related [[Controls]]==
 * Validation of the input data (CR and LF).
 * Forbid HTTP headers nesting in one header's field.
 * [[:Category:Input Validation]]
 ==References==
-TBD
+* TBD

@@ Line 77: / Line 77: @@
 *[[HTTP Response Splitting]]
-*[[Cache_Poisoning]]
+*[[Cache Poisoning]]
 ==Related [[Vulnerabilities]]==

@@ Line 11: / Line 11: @@
 This attack is rather difficult to carry out in the real environment. The list of conditions is long and hard to
-accomplish by the attacker. However it's easier to use this technique than Cross-User Defacement.
+accomplish by the attacker.
-Cross-User Defacement attack is possible because of HTTP_Response_Splitting and flaws in the web application.
+Cross-User Defacement attack is possible because of [[HTTP Response Splitting]] and flaws in the web application.
 It is crucial from the attacker's point of view that the application allows for filling the header field with
 more than one header using CR (Carrige Return) and LF (Line Feed) characters.

@@ Line 1: / Line 1: @@
 {{Template:Attack}}
 {{Template:Fortify}}
 ==Description==