This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Testing for WS Replay (OWASP-WS-007)"
Bruno Vernay (talk | contribs) m (removed ambiguity about TLS capability to prevent replay attack) |
|||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 7: | Line 7: | ||
== Description of the Issue == | == Description of the Issue == | ||
| − | A replay attack is a "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 WebScarab, a tester can resend a packet to the target 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 == | == Black Box testing and example == | ||
| − | '''Testing for Replay Attack | + | '''Testing for Replay Attack Vulnerabilities:''' |
1. 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 | 1. 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 17: | Line 17: | ||
[[Image: ReplayWireshark1.jpg]] | [[Image: ReplayWireshark1.jpg]] | ||
| − | 2. 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 | + | 2. 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]] | [[Image: ReplayWebScarab1.jpg]] | ||
| Line 23: | Line 23: | ||
'''Result Expected:''' | '''Result Expected:''' | ||
| − | The tester can assume the identity of | + | The tester can assume the identity of a user. |
== Gray Box testing and example == | == Gray Box testing and example == | ||
| Line 29: | Line 29: | ||
'''Testing for Replay Attack vulnerabilities | '''Testing for Replay Attack vulnerabilities | ||
| − | 1. Does the web service employ some means of preventing the replay attack | + | 1. 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); | string id = GetSessionIDMac().Substring (0, 24); | ||
| − | |||
... | ... | ||
| − | |||
private string GetSessionIDMac (string id, string ip, | private string GetSessionIDMac (string id, string ip, | ||
string agent, string key) | string agent, string key) | ||
| Line 50: | Line 48: | ||
| − | 2. Can the site employ SSL | + | 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 59: | Line 57: | ||
'''Tools''' | '''Tools''' | ||
| − | * OWASP WebScarab | + | * [[OWASP_WebScarab_Project|OWASP WebScarab]] |
* Ethereal - http://www.ethereal.com/ | * Ethereal - http://www.ethereal.com/ | ||
* Wireshark - http://www.wireshark.org/ (recommended instead of Ethereal - same developers, same codebase) | * Wireshark - http://www.wireshark.org/ (recommended instead of Ethereal - same developers, same codebase) | ||
* TCPReplay - http://tcpreplay.synfin.net/trac/wiki/manual | * TCPReplay - http://tcpreplay.synfin.net/trac/wiki/manual | ||
Latest revision as of 09:23, 14 June 2011
OWASP Testing Guide v3 Table of Contents
This article is part of the OWASP Testing Guide v3. The entire OWASP Testing Guide v3 can be downloaded here.
OWASP at the moment is working at the OWASP Testing Guide v4: you can browse the Guide here
Brief Summary
This section describes testing replay vulnerabilities of a web service. The threat for a replay attack is that the attacker can assume the identity of a valid user and commit some nefarious act without detection.
Description of the Issue
A replay attack is a "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 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
Testing for Replay Attack Vulnerabilities:
1. 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
2. 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.
Result Expected:
The tester can assume the identity of a user.
Gray Box testing and example
Testing for Replay Attack vulnerabilities
1. 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);
...
private string GetSessionIDMac (string id, string ip,
string agent, string key)
{
StringBuilder builder = new StringBuilder (id, 512);
builder.Append (ip.Substring (0, ip.IndexOf ('.',
ip.IndexOf ('.') + 1)));
builder.Append (agent);
using (HMACSHA1 hmac = new HMACSHA1
(Encoding.UTF8.GetBytes (key))) {
return Convert.ToBase64String (hmac.ComputeHash
(Encoding.UTF8.GetBytes (builder.ToString ())));
}
}
2. Can the site employ SSL? SSLv3.1 or TLSv1.0 will prevent unauthorized attempts to replay messages: Transport Layer Protection.
References
Whitepapers
- W3C: "Web Services Architecture" - http://www.w3.org/TR/ws-arch/
Tools
- 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
