+- Hack Forums (https://hackforums.net)
+-- Forum: Tech (https://hackforums.net/forumdisplay.php?fid=444)
+--- Forum: Coding (https://hackforums.net/forumdisplay.php?fid=151)
+---- Forum: Software Development (https://hackforums.net/forumdisplay.php?fid=118)
+---- Thread: [.NET] Cloudflare Bypass (/showthread.php?tid=5300480)
Pages: Pages
1
2
Cloudflare Bypass - debug - Jun 10, 2016
Credits to sizzuz for finding this originally: https://hackforums.net/showthread.php?tid=5295453
Basically this will create a webclient for any Cloudflare protected website, so that you get the cf clearance cookie, thus bypassing the bot protection.
C#: https://gist.github.com/gubed/8cccced275b39237d3e4cf5e2afe82f7
VB.NET: https://gist.github.com/gubed/6dccfa408b8ce85fe279f4aa85fd6952
There are likely VB conversion errors, just let me know.
Also, several minor things have been broken to prevent leeching. So don't ask me why it isn't working, I will not help you.
Example Usage:
PHP Code
<?php
WebClient c = CloudflareBypass.CFClient("https://fagdns.su");
MessageBox.Show(c.DownloadString("https://fagdns.su/aup.php"));
Enjoy
* - eCoLoGy - Jun 10, 2016
Nice share mate!
Haven't tested it but coming from you I assume it works just fine.
* - SL x TnT - Jun 10, 2016
(Jun 10, 2016 07:17 PM)eCoLoGy Wrote: Nice share mate!
Haven't tested it but coming from you I assume it works just fine.
There are a few bugs in it (intentional), but can be found easily.
First person I've seen on HF that extended the WebClient for the cookies, but why didn't you use it for your first request?
When I messed around with Cloudfare, a 6 second wait worked the best. 5 seconds worked for most sites, but was a little too quick for some.
For anyone that uses this, make sure you use the same user agent for each request.
* - Syncc - Jun 10, 2016
Cloudflare is going to patch this with all this rant about it.
* - Cecilia - Jun 11, 2016
Don't rek my site pls. Thanks, and good release. Saw the PHP version was only a matter of time before someone converted it.
* - Nick (Name) - Jun 11, 2016
Very appreciative about the release! I'll try it out tonight with a few sites that I have in mind! The minor bugs weren't that hard to find at all either ;)
* - Cecilia - Jun 11, 2016
(Jun 11, 2016 03:28 AM)Yani Wrote: I hope CF doesn't fix this with all the fuzz around it. There's so many legit uses for bypassing that stupid browser check.
Many illegitimate too...
I think cloudflare will patch this but will continue to use cookie checks and such.
I am quite sure that it will be able to be bypassed even after being patched.
* - Wardow - Jun 11, 2016
Why ever define a wait time, just place an handler on site refresh as the Javascript script will refresh the page after adding the cookie
* - Assault - Jun 11, 2016
(Jun 11, 2016 05:13 AM)Wardow Wrote: Why ever define a wait time, just place an handler on site refresh as the Javascript script will refresh the page after adding the cookie
.. because he's not using a web browser? those are raw web requests
* - +Haze - Jun 11, 2016
(Jun 10, 2016 02:42 PM)debug Wrote: Basically this will create a webclient for any Cloudflare protected website, so that you get the cf clearance cookie, thus bypassing the bot protection.
Actually the cloudflare protection isn't for bot protection, it's for DDoS protection.
(Jun 11, 2016 05:13 AM)Wardow Wrote: Why ever define a wait time, just place an handler on site refresh as the Javascript script will refresh the page after adding the cookie
You're stupid af.
Also, if cloudflare patch this, there is still another method to solve this that exists,
https://hackforums.net/showthread.php?tid=4530083
That works without fail. But nice work Debug, I like this.
My only thing I would of liked to see is if you had make the function return the cloudlfare clearance cookie value instead of return a webclient instance. This way we can do whatever we want with the cookie value right? This way we're not bound to using the WebClient, we can use any request object and just add the cookie value in or something.
* - Odus - Jun 11, 2016
(Jun 11, 2016 05:13 AM)Wardow Wrote: Why ever define a wait time, just place an handler on site refresh as the Javascript script will refresh the page after adding the cookie
If the refresh time is returned with the interstitial, it makes more sense to wait rather than transferring to/from handlers.
* - SIM-3167319 - Jun 12, 2016
Its a nice share, crawling cludflare sites is a shitty without bypasse
i remember when i coded on project using webbrowser controls to craw!
* - Decim - Jun 13, 2016
(Jun 11, 2016 05:13 AM)Wardow Wrote: Why ever define a wait time, just place an handler on site refresh as the Javascript script will refresh the page after adding the cookie
Care to elaborate? Curious.
* - Wardow - Jun 13, 2016
(Jun 11, 2016 08:02 AM)Assault Wrote: .. because he's not using a web browser? those are raw web requests
"WebClient",
Got confused, sorry
(Jun 13, 2016 06:50 AM)Arcanecfg Wrote: Care to elaborate? Curious.
Wait until the page attempt to refresh and save the cookies at that time
* - LordCoder - Jun 13, 2016
I was actually looking to bypass CloudFlare _cf cookie, as some web requests were just returning some random shit. Nice share.
BTW Nice array [-1] Hahaha