Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Super Bot Fight Mode blocks RDP access #556

Open
mastercoms opened this issue Jan 31, 2022 · 4 comments
Open

Super Bot Fight Mode blocks RDP access #556

mastercoms opened this issue Jan 31, 2022 · 4 comments
Labels
Good first issue Type: Bug

Comments

@mastercoms
Copy link

@mastercoms mastercoms commented Jan 31, 2022

Hi, I was having trouble connecting to a tunnel for RDP access and tried all suggested tips. After some luck, I found that this access was blocked in the firewall logs as:

Bot Fight Mode for Definite Bots
manage definite bots

Managed Challenge

So, I set Super Bot Fight Mode: Definitely automated to Allow and it works now.

Is this a documentation issue (should note allowing definite bots is required) or a CloudFlare rules issue (this traffic should not be detected as a bot)? I would prefer keeping the protection for bots, but I suppose I can also split out our domains between our teams and public URLs.

@mastercoms mastercoms changed the title Super Bot Fifht Super Bot Fight Mode blocks RDP access Jan 31, 2022
@abelinkinbio abelinkinbio added Type: Bug Good first issue labels Jan 31, 2022
@abelinkinbio
Copy link
Collaborator

@abelinkinbio abelinkinbio commented Jan 31, 2022

Thanks for flagging this one. This sounds like a rules issue, but we'll take a look and confirm. Also, are you using cloudflared access or warp on the client side? Do you have a screenshot you'd be able to share of redacted logs as well?

@mastercoms
Copy link
Author

@mastercoms mastercoms commented Jan 31, 2022

Thank you! It was cloudflared access rdp.

The client failed with failed to connect to origin error="websocket: bad handshake".

This is the firewall event:

{
  "action": "managed_challenge",
  "clientASNDescription": "REDACTED",
  "clientAsn": "REDACTED",
  "clientCountryName": "US",
  "clientIP": "REDACTED",
  "clientRequestHTTPHost": "REDACTED",
  "clientRequestHTTPMethodName": "GET",
  "clientRequestHTTPProtocol": "HTTP/1.1",
  "clientRequestPath": "/",
  "clientRequestQuery": "",
  "datetime": "REDACTED",
  "rayName": "REDACTED",
  "ruleId": "874a3e315c344b1281ad4f00046aab6f",
  "rulesetId": "48ba18287c544bd7bdbe842a294f1ae2",
  "source": "firewallManaged",
  "userAgent": "Go-http-client/1.1",
  "matchIndex": 0,
  "metadata": [
    {
      "key": "ruleset_version",
      "value": "4"
    },
    {
      "key": "version",
      "value": "3"
    },
    {
      "key": "type",
      "value": "customer"
    }
  ],
  "sampleInterval": 1
}

I was able to connect to the CloudFlare access domain from within the browser and access the 200 OK page. I suppose the Go-http-client agent classifies this request as automated, which is fair enough.

@jhult
Copy link

@jhult jhult commented Feb 1, 2022

We are seeing things like git/Gitea be blocked:

git/2.30.1 (Apple Git-130) (Darwin Kernel Version 21.2.0: Sun Nov 28 20:28:54 PST 2021; root:xnu-8019.61.5~1/RELEASE_X86_64 21.2.0; darwin x64) vscode/1.63.2 (Visual Studio Code)

Query string: ?service=git-upload-pack
Service: Bot fight mode
Action taken: JS Challenge

@jhult
Copy link

@jhult jhult commented Feb 2, 2022

Looks like Jenkins build jobs are also being blocked:

Query string: ?delay=0sec
Service: Bot fight mode
Action taken: JS Challenge

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Good first issue Type: Bug
Projects
None yet
Development

No branches or pull requests

3 participants