WitnessMe | Web Inventory tool , takes screenshots | Security Testing library

by byt3bl33d3r Python Version: 1.5.0 License: GPL-3.0

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

kandi X-RAY | WitnessMe Summary

WitnessMe is a Python library typically used in Testing, Security Testing applications. WitnessMe has no bugs, it has no vulnerabilities, it has build file available, it has a Strong Copyleft License and it has low support. You can install using 'pip install WitnessMe' or download it from GitHub, PyPI.

WitnessMe is primarily a Web Inventory tool inspired by Eyewitness, its also written to be extensible allowing you to create custom functionality that can take advantage of the headless browser it drives in the back-end. WitnessMe uses the Pyppeteer library to drive Headless Chromium.

Support

Quality

Security

License

Reuse

Support

WitnessMe has a low active ecosystem.

It has 672 star(s) with 103 fork(s). There are 24 watchers for this library.

It had no major release in the last 12 months.

There are 16 open issues and 16 have been closed. On average issues are closed in 96 days. There are 7 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of WitnessMe is 1.5.0

Quality

WitnessMe has 0 bugs and 0 code smells.

Security

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

WitnessMe code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

WitnessMe is licensed under the GPL-3.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

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

Deployable package is available in PyPI.

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

Installation instructions, examples and code snippets are available.

WitnessMe saves you 962 person hours of effort in developing the same functionality from scratch.

It has 2191 lines of code, 130 functions and 28 files.

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

Top functions reviewed by kandi - BETA

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

Script entry point
The main loop
Patch pyppeteer
Exit exit
Callback function for parsing reports
Gets a single scan
Take screenshot
Resolve an IP address
Check if host is an IP address
Called when a response is received
Callback called when a node is received
Grab page
Run the target generator
Start a headless browser
Open a browser
Create new targets
Print results
Upload file to scan
Return the result of a scan
Patch Pyppeteer
Grab an object
Start a scan
Take a screenshot
Create a ScreenShot object
Add results to scan database
Stop a scan

Get all kandi verified functions for this library.

WitnessMe Key Features

No Key Features are available at this moment for WitnessMe.

WitnessMe Examples and Code Snippets

No Code Snippets are available at this moment for WitnessMe.

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 WitnessMe

You really should only install WitnessMe this way if you intend to hack on the source code. You're going to Python 3.7+ and Poetry: please refer to the Poetry installation documentation in order to install it.

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: