SubDomainizer | find subdomains and interesting things | Security Testing library

by nsonaniya2010 Python Version: v2.0 License: MIT

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

kandi X-RAY | SubDomainizer Summary

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

SubDomainizer is a tool designed to find hidden subdomains and secrets present is either webpage, Github, and external javascripts present in the given URL. This tool also finds S3 buckets, cloudfront URL's and more from those JS files which could be interesting like S3 bucket is open to read/write, or subdomain takeover and similar case for cloudfront. It also scans inside given folder which contains your files.

Support

Quality

Security

License

Reuse

Support

SubDomainizer has a medium active ecosystem.

It has 1485 star(s) with 228 fork(s). There are 41 watchers for this library.

It had no major release in the last 12 months.

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

It has a neutral sentiment in the developer community.

The latest version of SubDomainizer is v2.0

Quality

SubDomainizer has 0 bugs and 39 code smells.

Security

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

SubDomainizer code analysis shows 9 unresolved vulnerabilities (0 blocker, 9 critical, 0 major, 0 minor).

There are 6 security hotspots that need review.

License

SubDomainizer is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

SubDomainizer releases are available to install and integrate.

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

Installation instructions, examples and code snippets are available.

SubDomainizer saves you 227 person hours of effort in developing the same functionality from scratch.

It has 555 lines of code, 24 functions and 1 files.

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

Top functions reviewed by kandi - BETA

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

Gather info from cloud services
Extracts inline javascript files
Gets all urls from Github .
a wrapper for subextractor
Pre - compile regex .
Sort a list of subdomain names .
Get folder data from root folder
Pre - compiled regex
Get git data from GitHub
Generate a logo .

Get all kandi verified functions for this library.

SubDomainizer Key Features

No Key Features are available at this moment for SubDomainizer.

SubDomainizer Examples and Code Snippets

SUBDOMAIN

PHP

Lines of Code : 5

License : No License

Copy

  createSubdomain("SUBDOMAIN", "PATH");

subdomainator,Installation

Python

Lines of Code : 4

License : No License

Copy

git clone https://github.com/skorov/subdomainator.git
cd subdomainator
pip install -r requirements.txt
python subdomainator_cli.py

Subdomain searcher

Python

Lines of Code : 1

License : No License

Copy

Python subdomain_searcher.py -d domainname.com -s

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