Afrikaans
Akan
Albanian
Amharic
Armenian
Azerbaijani
Basque
Belarusian
Bemba
Bengali
Bihari
Bosnian
Breton
Bulgarian
Cambodian
Catalan
Cebuano
Cherokee
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
English
Esperanto
Estonian
Ewe
Faroese
Filipino
Finnish
French
Frisian
Ga
Galician
Georgian
German
Greek
Guarani
Gujarati
Haitian Creole
Hausa
Hawaiian
Hebrew
Hindi
Hmong
Hungarian
Icelandic
Igbo
Indonesian
Interlingua
Irish
Italian
Japanese
Javanese
Kannada
Kazakh
Kinyarwanda
Kirundi
Kongo
Korean
Krio (Sierra Leone)
Kurdish
Kurdish (Soranรฎ)
Kyrgyz
Laothian
Latin
Latvian
Lingala
Lithuanian
Lozi
Luganda
Luo
Luxembourgish
Macedonian
Malagasy
Malay
Malayalam
Maltese
Maori
Marathi
Mauritian Creole
Moldavian
Mongolian
Myanmar (Burmese)
Montenegrin
Nepali
Nigerian Pidgin
Northern Sotho
Norwegian
Norwegian (Nynorsk)
Occitan
Oriya
Oromo
Pashto
Persian
Polish
Portuguese (Brazil)
Portuguese (Portugal)
Punjabi
Quechua
Romanian
Romansh
Runyakitara
Russian
Samoan
Scots Gaelic
Serbian
Serbo-Croatian
Sesotho
Setswana
Seychellois Creole
Shona
Sindhi
Sinhalese
Slovak
Slovenian
Somali
Spanish
Spanish (Latin American)
Sundanese
Swahili
Swedish
Tajik
Tamil
Tatar
Telugu
Thai
Tigrinya
Tonga
Tshiluba
Tumbuka
Turkish
Turkmen
Twi
Uighur
Ukrainian
Urdu
Uzbek
Vietnamese
Welsh
Wolof
Xhosa
Yiddish
Yoruba
Zulu
0 Hello everyone. 1
So in this video we are going to see how we can achieve No-Rate limit protection bypass. 2
Number two. 3
So in this video we will see how we can bypass No-Rate limit using x forwarded host header into any request. 4
So for this we are going to see a report right now to understand this better of bypassing rate limit 5
protection by spoofing originating IP. 6
So let's see what the user was able to do. 7
The first screenshot They blocked my IP as you can see this user was performing an action in which there 8
is a WAF which is blocking as you can see 403 forbidden now trying to host header injection which means 9
modifying the host from the www.example.com to www.xyz.com 10
adding x forwarded host hacker.com but still no success. 11
Now trying for X forwarded for option to spoof originating IP address. 12
So we are going to give a random IP address in X forwarded for still no success. 13
Now trying with X forwarded for IP header into the request twice two times instead of one thing and 14
you can see we were successfully able to bypass this No-Rate limit protection because the application 15
is giving 200 ok right now. 16
So what is the lesson learned the lesson learned is that you can bypass no rate limit by applying or 17
digital header it like X forwarded for or X forwarded in the request X for x-forwarded host in the request. 18
So let's get back to the presentation and let us No-Rate limit by ad adding some specific headers 19
so you can add headers with the request like x-originating IP and you can give any random IP X 20
forwarded for that we already saw into the report X remote IP, X remote address, x client IP X host and 21
X forwarded host we already saw X forwarded host and X forwarded for through which the user was able to bypass 22
the no rate limit. 23
So this is one of the way in the bypass number two in which you can bypass the no rate limit protection 24
so the first one understood we understood the second one also third is remote IP remote address client 25
IP X host and X forwarded host so practical time. 26
So let's see what we can achieve through this. 27
And I have written a small script to explain this to you guys. 28
So let me just open the script. 29
nano check.py 30
So this is a Python script which basically add these headers the headers that we understood into the 31
slide and sent the request to the specific target you want to send to. 32
Okay. 33
So you have to use like this python check IP domain name. 34
http or https 35
And you have to send the request. 36
So let's see how to use this. 37
I already run it couple of times so you can see from your python check.py www.udemy.com 38
HTTPS as you can see for the first header we added the status code was 200 response-size was this. 39
This is nothing but the response length x-forwarded host a response and changed remote IP length change 40
at a remote address length changed client IP length remains the same X host Length change forwarded host 41
length remains the same X this one and this one. 42
So basically in this we can see the application that is udemy.com behaves in a different manner 43
when different different headers are been sent. 44
So yeah we can try for no rate limit by adding a new header each time as we can see there is some change 45
into the response. 46
Similarly I tried on Instagram and Instagram. 47
Also we were able to see changes into the into the response by adding new headers. 48
Similarly I tried on no broker but this time the response was same for everything because they are not 49
parsing anything like this and no rate limit is fixed on their website and which cannot be bypassed 50
anymore. 51
99 acers is still the same on Tinder.com still the same. 52
We are not able to perform no rate limit by bypassing by adding any of the headers I will attach this 53
code in the description and you guys can utilize this for your testing. 54
I hope you guys understood. 55
Thank you so much.
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.