CloudFlair | 🔎 Find origin servers of websites behind CloudFlare | Security Testing library

by christophetd Python Version: Current License: No License

X-Ray Key Features Code Snippets(3)Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | CloudFlair Summary

CloudFlair is a Python library typically used in Testing, Security Testing applications. CloudFlair has no bugs, it has no vulnerabilities, it has build file available and it has medium support. You can download it from GitHub.

CloudFlair is a tool to find origin servers of websites protected by CloudFlare who are publicly exposed and don't restrict network access to the CloudFlare IP ranges as they should. The tool uses Internet-wide scan data from Censys to find exposed IPv4 hosts presenting an SSL certificate associated with the target's domain name. For more detail about this common misconfiguration and how CloudFlair works, refer to the companion blog post at Here's what CloudFlair looks like in action. (The IP addresses in this example have been obfuscated and replaced by randomly generated IPs).

Support

Quality

Security

License

Reuse

Support

CloudFlair has a medium active ecosystem.

It has 1914 star(s) with 300 fork(s). There are 52 watchers for this library.

It had no major release in the last 6 months.

There are 0 open issues and 50 have been closed. On average issues are closed in 181 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of CloudFlair is current.

Quality

CloudFlair has 0 bugs and 0 code smells.

Security

CloudFlair has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

CloudFlair code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

CloudFlair does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

CloudFlair releases are not available. You will need to build from source code and install.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

CloudFlair saves you 98 person hours of effort in developing the same functionality from scratch.

It has 264 lines of code, 15 functions and 5 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed CloudFlair and discovered the below as its top functions. This is intended to give you an instant insight into CloudFlair implemented functionality, and help decide if they suit your requirements.

Finds and returns a list of hosts
Get trusted certificates
Given a list of certificates return a list of hosts
Checks if the given domain is a CloudFlare IP
Check if a domain is a valid DNS domain
Check if given ip is a cloudflare IP
Filter out cloudflare IPs
Find candidate origin servers
Retrieve the original homepage
Get a random user agent
Gets CloudFlare IP ranges
Save a list of origins to a file
Print origins
Prints a list of hosts

Get all kandi verified functions for this library.

CloudFlair Key Features

No Key Features are available at this moment for CloudFlair.

CloudFlair Examples and Code Snippets

Cloudflair,Usage,Call An API Endpoint

Ruby

Lines of Code : 29

License : Permissive (MIT)

Copy

require 'cloudflair'

# GET https://api.cloudflare.com/client/v4/railguns
Cloudflair.railguns
# => [...]

# GET https://api.cloudflare.com/client/v4/zones
Cloudflair.zones
# => [...]

# GET https://api.cloudflare.com/client/v4/zones/cd7d068de30

Cloudflair,Usage,Configuration

Ruby

Lines of Code : 13

License : Permissive (MIT)

Copy

require 'cloudflair'
Cloudflair.configure do |config|
  config.cloudflare.auth.key = 'YOUR_API_KEY'
  config.cloudflare.auth.email = 'YOUR_ACCOUNT_EMAIL'
  # if you have a user_service_key, you don't need auth.key and auth.email
  config.cloudflare.a

default

Python

Lines of Code : 4

License : No License

Copy

acme.com - 200
acme.com/backlog/ - 404
acme.com/controlpanel/ - 401 <-- dig deeper
acme.com/controlpanel/[bruteforce here now]

Community Discussions

Trending Discussions on Security Testing

DAST security scaning of a IoT Nodemcu esp8266 LUA script www HTML server connected to camera and A/C relay

QUESTION

DAST security scaning of a IoT Nodemcu esp8266 LUA script www HTML server connected to camera and A/C relay

Asked 2021-Apr-08 at 01:04

I have not, but shall DAST* security test, out of curiosity, an IoT device; Nodemcu esp8266 www server I built. It's showing a HTML page (on a mobile phone for example) that allows to control and interact with a camera module and a A/C relay. With it I can for example show images captured in the camera I even think it has some image recognition built in, and I can switch on and off a relay for electrical current to a light bulb (110/220v A/C power)

Before I start pentest I though I better start thinking of what types of exploits one would be able to find and detect? Which sinister exploits I will be able to find, or rather ought be able to find given a proper pentest exercise? (And if I do not find exploits, my approach to the pentest of the Iot might be wrong)

I ponder it might be a totally pointless exercise since the esp8266 www server (or rather its LUA programming libraries) might not have any security built into it, so basically it is "open doors" and everything with it is unsafe ?

The test report might just conclude what I can foresee be that the the "user input needs to be sanitized"?

Anyone have any idea what such pentest of a generic IoT device generally reports? Maybe it is possible to crash or reset the IoT device? Buffer overruns, XXS, call own code ?

I might use ZAP or Burpsuite or similar DAST security test tool.

I could of course SAST test it instead, or too, but I think it will be hard to find a static code analyzer for the NodeMCU libraries and NUA scripting language easily ? I found some references here though: https://ieeexplore.ieee.org/abstract/document/8227299 but it seems to be a long read.

So if someone just have a short answer what to expect in a DAST scan/pentest , it would be much appreciated.

Stay safe and secure out there ! Zombieboy

...

ANSWER

Answered 2021-Apr-08 at 01:04

I do my vulnerability scanning with OpenVAS (I assume this is what you mean by pentesting?). I am not aware of any IOT focused Tools.

If your server is running on esp8266, i would imagine that there is no much room for authentication and encryption of http traffic, but correct me if i am wrong).

Vulnerability Scan results might show things like unencrypted http traffic, credentials transmitted in cleartext (if you have any credentials fields in the pages served by the web server) etc. Depending on if there is encryption, you might also see weak encryption findings.

You might get some false positives on your lua webserver reacting like other known webservers when exploits are applied. I have seen this kind of false positive specially on DoS vulnerabilities when a vulnerability scan is testing a vulnerability and the server becomes unresponsive. Depending on how invasive your vulnerability scanner is, you might get a lot of false positives for DoS on such a constrained platform.

Source https://stackoverflow.com/questions/66995125

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install CloudFlair

Register an account (free) on https://censys.io/register
Browse to https://censys.io/account/api, and set two environment variables with your API ID and API secret
Clone the repository
Install the dependencies
Run CloudFlair (see Usage below for more detail)

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: