Application Level DoS Methods

1. Email Bounce Issues

  • Check if Application has Invite Functionality

  • Try sending Invites to Invalid Email Accounts

  • Try to find Email Service Provider such as AWS SES , Hubspot , Campaign Monitor Note: You can find Email Service Provider by checking Email Headers

  • Once you have the Email Service Provider, Check there Hard Bounce Limits. Here are the limits for some of them:

    1. Hubspot Hard bounces: HubSpot's hard bounce limit is 5%. For reference, many ISPs prefer bounce rates to be under 2%.

    2. AWS SES: The rate of SES ranges from first 2-5% then 5-10%

Impact: Once the Hard Bounce Limits are reached, Email Service Provider will block the Company which means, No Emails would be sent to the Users !

2. Long Password DoS Attack

  • As the value of password is hashed and then stored in Databases. If there is no limit on the length of the Password, it can lead to consumption of resources for Hashing the Long Password.

How to test?

  • Use a Password of length around 150-200 words to check the presense of Length Restriction

  • If there is no Restriction, Choose a longer password and keep a eye on Response Time

  • Check if the Application Crashes for few seconds

Where to test?

  • Registration Password Field is usually restricted but the Length of Password on the Forgot Password Page and the Change Password (As Authenticated User) Functionality is usually missing.

3. Long String DOS

  • When you set some string so long so server cannot process it anymore it cause DOS sometime

How to test

Create app and put field like username or address or even profile picture name parameter ( second refrence ) like 1000 character of string . 
Search A's account from B's account either it will
  • Either it will keeping on searching for long time

  • Either the application will crash (500 - Error Code)

Use Password From Password.txt

⚠️it's not recommended using more than 5000 characters as password.

4. Permanent DOS to victim

This is not Application Level DOS but a Permanent DOS to victim. In some website user get blocked after trying to loging in with wrong credidentials.We will untilize this feature as bug :D.

How to check.

  • Go to login page of

  • Now enter valid account email and wrong password .

  • Try to login with these details for few times(at least 10-20 times).You can use repeater or intruder in burpsuite.

  • If your account get blocked, check the blocking time period.If the blocking time period is more than 30 min .You can report it.

Point to Remember

  • Make sure there is no captcha during login because we cann't make any automated tool to loop the request.

  • Make sure Old session are expired after being blocked.

What is priority of this bug?

  • If the user get permanently block after some wrong attempts this is considered as P2.

  • If the user get temporarly block this is considered as P3/P4.

During report try to add impact by saying that you can permanently block user account by looping this request with some intervals.

Reference :

- Email Bounce Issues

- Long Password DoS Attack




- Long String DOS

- Permanent DOS to victim



Last updated