Testing for WS Replay (OWASP-WS-007) - Revision history

Bruno Vernay: removed ambiguity about TLS capability to prevent replay attack

2011-06-14T09:23:55Z

removed ambiguity about TLS capability to prevent replay attack

KirstenS: /* Gray Box testing and example */

2009-02-10T01:51:30Z

‎Gray Box testing and example

KirstenS: /* Gray Box testing and example */

2009-02-10T01:51:03Z

‎Gray Box testing and example

KirstenS: Testing for WS Replay moved to Testing for WS Replay (OWASP-WS-007)

2008-12-15T23:58:45Z

Testing for WS Replay moved to Testing for WS Replay (OWASP-WS-007)

KirstenS: /* Black Box testing and example */

2008-12-14T02:54:05Z

‎Black Box testing and example

Namn at 13:25, 2 September 2008

2008-09-02T13:25:54Z

KirstenS: /* Description of the Issue */

2008-08-30T23:25:26Z

‎Description of the Issue

KirstenS: /* References */

2008-08-30T23:24:59Z

‎References

KirstenS: /* Description of the Issue */

2008-08-30T23:23:25Z

‎Description of the Issue

Mmeucci at 12:48, 22 August 2008

2008-08-22T12:48:54Z

← Older revision		Revision as of 09:23, 14 June 2011
Line 48:		Line 48:


−	2. Can the site employ SSL ~~- this~~ will prevent unauthorized attempts to replay messages?	+	2. Can the site employ SSL? SSLv3.1 or TLSv1.0 will prevent unauthorized attempts to replay messages: [[Transport Layer Protection Cheat Sheet#Benefits\|Transport Layer Protection]].

	== References ==		== References ==

@@ Line 32: / Line 32: @@
      string id = GetSessionIDMac().Substring (0, 24);
      ...
      private string GetSessionIDMac (string id, string ip,
          string agent, string key)

@@ Line 29: / Line 29: @@
 '''Testing for Replay Attack vulnerabilities
-. Does the web service employ some means of preventing the replay attack?  Such as pseudo random Session tokens, Nonces with MAC addresses or Timestamping.  Here is an example of an attempt to randomize session tokens: (from MSDN Wicked Code - http://msdn.microsoft.com/msdnmag/issues/04/08/WickedCode/default.aspx?loc=&fig=true#fig1).
+. Does the web service employ some means of preventing the replay attack such as pseudo random Session tokens, Nonces with MAC addresses, or Timestamping?  Here is an example of an attempt to randomize session tokens: (from MSDN Wicked Code - http://msdn.microsoft.com/msdnmag/issues/04/08/WickedCode/default.aspx?loc=&fig=true#fig1).
      string id = GetSessionIDMac().Substring (0, 24);

@@ Line 11: / Line 11: @@
 == Black Box testing and example ==
-'''Testing for Replay Attack vulnerabilities:'''
+'''Testing for Replay Attack Vulnerabilities:'''
 . Using Wireshark on a network, sniff traffic and filter for web service traffic. Another alternative is to install WebScarab and use it as a proxy to capture http traffic

@@ Line 7: / Line 7: @@
 == Description of the Issue ==
-A replay attack is a "[[Man-in-the-middle_attack|man-in-the-middle]]" type of attack where a message is intercepted and replayed by an attacker to impersonate the original sender.  For web services, as with other types of HTTP traffic, a sniffer such as Ethereal or Wireshark can capture traffic posted to a web service and using a tool like [[OWASP_WebScarab_Project|WebScarab]], a tester can resend a packet to the target server.  An attacker can attempt to resend the original message or change the message in order to compromise the host server.
+A replay attack is a "[[Man-in-the-middle_attack|man-in-the-middle]]" type of attack where a message is intercepted and replayed by an attacker to impersonate the original sender.  For web services, as with other types of HTTP traffic, a sniffer such as Ethereal or Wireshark can capture traffic posted to a web service and using a tool like [[OWASP_WebScarab_Project|WebScarab]], a tester can resend a packet to the target server.  A tester can attempt to resend the original message or change the message in order to compromise the host server.
 == Black Box testing and example ==
@@ Line 17: / Line 17: @@
 [[Image: ReplayWireshark1.jpg]]
-. Using the packets captured by ethereal, use TCPReplay to initiate the replay attack by reposting the packet.  It may be necessary to capture many packets over time to determine session id patterns in order to assume a valid session id for the replay attack.  It is also possible to manually post captured HTTP traffic, by using WebScarab
+. Using the packets captured by ethereal, use TCPReplay to initiate the replay attack by reposting the packet.  It may be necessary to capture many packets over time to determine session id patterns in order to assume a valid session id for the replay attack.  It is also possible to manually post captured HTTP traffic, by using WebScarab.
 [[Image: ReplayWebScarab1.jpg]]
@@ Line 23: / Line 23: @@
 '''Result Expected:'''
-The tester can assume the identity of the attacker.
+The tester can assume the identity of a user.
 == Gray Box testing and example ==

← Older revision	Revision as of 23:58, 15 December 2008
(No difference)

@@ Line 59: / Line 59: @@
 '''Tools'''
-* OWASP WebScarab - http://www.owasp.org/index.php/Category:OWASP_WebScarab_Project
+* [[OWASP_WebScarab_Project|OWASP WebScarab]]
 * Ethereal - http://www.ethereal.com/
 * Wireshark - http://www.wireshark.org/ (recommended instead of Ethereal - same developers, same codebase)
 * TCPReplay - http://tcpreplay.synfin.net/trac/wiki/manual

@@ Line 1: / Line 1: @@
-[[http://www.owasp.org/index.php/Web_Application_Penetration_Testing_AoC Up]]<br>
+{{Template:OWASP Testing Guide v3}}
 == Brief Summary ==
@@ Line 64: / Line 63: @@
 * Wireshark - http://www.wireshark.org/ (recommended instead of Ethereal - same developers, same codebase)
 * TCPReplay - http://tcpreplay.synfin.net/trac/wiki/manual