vulnSpiderCrawl | About vulnerability crawling and intelligence gathering | Security Testing library

by Qclover Python Version: Current License: No License

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

kandi X-RAY | vulnSpiderCrawl Summary

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

The original intention of the project is to crawl and update vulnerabilities (including vulnerability name, vulnerability number, vulnerability POC link, vulnerability update time) in time, and call Vuln interface of shodan's API synchronously to acquire the corresponding assets IP in real time, and send the most regular mail every day. New vulnerabilities, and finally establish a vulnerability Threat Intelligence database, through real-time collection of data, real-time updates to the database, establish a search index, through the query of keywords, get the details of other vulnerabilities and related threats IP. Current progress: real time crawling of vulnerabilities. Difficulty: Shodan's Vuln interface free channel has been closed. Tasks: email alert, data access and search index.

Support

Quality

Security

License

Reuse

Support

vulnSpiderCrawl has a low active ecosystem.

It has 1 star(s) with 1 fork(s). There are no watchers for this library.

It had no major release in the last 6 months.

vulnSpiderCrawl has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of vulnSpiderCrawl is current.

Quality

vulnSpiderCrawl has no bugs reported.

Security

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

License

vulnSpiderCrawl 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

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

vulnSpiderCrawl has no build file. You will be need to create the build yourself to build the component from source.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of vulnSpiderCrawl

Get all kandi verified functions for this library.

vulnSpiderCrawl Key Features

No Key Features are available at this moment for vulnSpiderCrawl.

vulnSpiderCrawl Examples and Code Snippets

No Code Snippets are available at this moment for vulnSpiderCrawl.

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 vulnSpiderCrawl

You can download it from GitHub.
You can use vulnSpiderCrawl like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

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: