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 Denial of Service"
| Line 1: | Line 1: | ||
| − | + | {{Template:OWASP Testing Guide v3}} | |
| − | {{Template:OWASP Testing Guide | ||
''' 4.7 Denial of Service Testing ''' | ''' 4.7 Denial of Service Testing ''' | ||
| Line 10: | Line 9: | ||
Here are the DoS testings we will talk about: | Here are the DoS testings we will talk about: | ||
| − | + | ||
| + | #[[Testing_for_SQL_Wildcard_Attacks]] | ||
#[[DoS Testing: Locking Customer Accounts]] | #[[DoS Testing: Locking Customer Accounts]] | ||
#[[DoS Testing: Buffer Overflows]] | #[[DoS Testing: Buffer Overflows]] | ||
| Line 25: | Line 25: | ||
<br> | <br> | ||
| − | |||
[[Category:Denial of Service Attack]] | [[Category:Denial of Service Attack]] | ||
Revision as of 15:53, 14 August 2008
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
4.7 Denial of Service Testing
The most common type of denial of service (DoS) attack is the kind used on a network to make a server unreachable by other valid users. The fundamental concept of a network DoS attack is a malicious user flooding enough traffic to a target machine, that it renders the target incapable of keeping up with the volume of requests it is receiving. When the malicious user uses a large number of machines to flood traffic to a single target machine, this is generally known as a distributed denial of service (DDoS) attack. These types of attacks are generally beyond the scope of what an application developer can prevent within their own code. This type of “battle of the network pipes” is best mitigated via network architecture solutions.
There are, however, types of vulnerabilities within applications that can allow a malicious user to make certain functionality or sometimes the entire website unavailable. These problems are caused by bugs in the application, often resulting from malicious or unexpected user input. This section will focus on application layer attacks against availability that can be launched by just one malicious user on a single machine.
Here are the DoS testings we will talk about:
- Testing_for_SQL_Wildcard_Attacks
- DoS Testing: Locking Customer Accounts
- DoS Testing: Buffer Overflows
- DoS Testing: User Specified Object Allocation
- DoS Testing: User Input as a Loop Counter
- DoS Testing: Writing User Provided Data to Disk
- DoS Testing: Failure to Release Resources
- DoS Testing: Storing too Much Data in Session
References
Stephen de Vries, Application denial of service (DoS) attacks: http://www.corsaire.com/white-papers/040405-application-level-dos-attacks.pdf
