web-exploitation-engine | Generic Command Exploitation Engine | Security Testing library

by infodox Python Version: Current License: No License

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

kandi X-RAY | web-exploitation-engine Summary

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

web exploitation engine - generic command injection exploitation utility. this is a simple enough utility written to exploit command injection bugs in web applications. i had abandoned this project a while ago, then saw the brilliant "rce.py" tool written by @lanmaster53, and saw his elegant solution to the "how to denote where to put the payload" problem, so i shamelessly ripped his code to write this. this tool can either give an inline shell like the original rce.py (it uses the same functions, just rewritten to suit), or a reverse shell. currently it only supports a base64 encoded reverse tcp shell payload, however the magic of the "payloads" module is that you can actually expand it. you just have to do a little work to add more payloads. so, how do i use this. the only mandatory argument is --url='url here'. in the url, using the tag, you specify where to inject code in the request. for example: h4x# ./we.py --url='' shell> id

Support

Quality

Security

License

Reuse

Support

web-exploitation-engine has a low active ecosystem.

It has 29 star(s) with 20 fork(s). There are 3 watchers for this library.

It had no major release in the last 6 months.

web-exploitation-engine has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of web-exploitation-engine is current.

Quality

web-exploitation-engine has 0 bugs and 0 code smells.

Security

web-exploitation-engine has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

web-exploitation-engine code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

web-exploitation-engine 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

web-exploitation-engine releases are not available. You will need to build from source code and install.

web-exploitation-engine has no build file. You will be need to create the build yourself to build the component from source.

web-exploitation-engine saves you 27 person hours of effort in developing the same functionality from scratch.

It has 75 lines of code, 7 functions and 4 files.

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

Top functions reviewed by kandi - BETA

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

Inject payload
Reverse the SSH server .
Main entry point .
Inner loop .
Do a reverse shell
Binds the connection
Display a banner for security vulnerabilities .

Get all kandi verified functions for this library.

web-exploitation-engine Key Features

No Key Features are available at this moment for web-exploitation-engine.

web-exploitation-engine Examples and Code Snippets

No Code Snippets are available at this moment for web-exploitation-engine.

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 web-exploitation-engine

You can download it from GitHub.
You can use web-exploitation-engine 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: