PowerHub | post exploitation tool based on a web application | Security Testing library

by AdrianVollmer PowerShell Version: 2.0.8 License: MIT

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

kandi X-RAY | PowerHub Summary

PowerHub is a PowerShell library typically used in Testing, Security Testing applications. PowerHub has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

PowerHub is a convenient post exploitation tool for PowerShell which aids a pentester in transferring data, in particular code which may get flagged by endpoint protection. Check out the [Wiki] Features:. During an engagement where you have a test client available, one of the first things you want to do is run PowerSploit. So you need to download the files, messing with endpoint protection, disable the execution policy, etc. PowerHub provides an (almost) one-click-solution for this. Oh, and you can also run arbitrary binaries (PE and shell code) entirely in-memory using PowerSploit’s modules, which is sometimes useful to bypass application whitelisting. Your loot (Kerberos tickets, passwords, etc.) can be easily transferred back either as a file or a text snippet, via the command line or the web interface. PowerHub also helps with collaboration in case you’re a small team.

Support

Quality

Security

License

Reuse

Support

PowerHub has a low active ecosystem.

It has 612 star(s) with 104 fork(s). There are 17 watchers for this library.

There were 2 major release(s) in the last 12 months.

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

It has a neutral sentiment in the developer community.

The latest version of PowerHub is 2.0.8

Quality

PowerHub has 0 bugs and 0 code smells.

Security

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

PowerHub code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

PowerHub 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

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

Installation instructions, examples and code snippets are available.

PowerHub saves you 1220 person hours of effort in developing the same functionality from scratch.

It has 2858 lines of code, 160 functions and 44 files.

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

Top functions reviewed by kandi - BETA

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

Import all modules
Determine the module type to use
Download the contents of the wheel
Build a wheel
Process files
Process a file
Determine the file type from the file
Saves the contents of the given file
Download a file
Create the payload
Install custom repo
Reload modules
Import modules
Encrypt a payload
Show loot box
Run webdav
Render modules
Show hub
Watch for blackhole folders
Start web server
Add content to clipboard
Return a list of loot items
Decorator to require authentication
Get the secret key
Run flask app
Start webdav
Encrypt data
Show filelist

Get all kandi verified functions for this library.

PowerHub Key Features

No Key Features are available at this moment for PowerHub.

PowerHub Examples and Code Snippets

No Code Snippets are available at this moment for PowerHub.

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 PowerHub

PowerHub itself does not need to be installed. Just execute powerhub.py. However, there are a few dependencies. They are listed in the [requirements.txt](https://github.com/AdrianVollmer/PowerHub/blob/master/requirements.txt). Install them either via pip3 install --user -r requirements.txt or use a virtual environment. If you do want to install PowerHub, you should do pip3 install --user .. Python2 is not supported. For building the payloads, you need the MinGW GCC and Mono C# compilers. On Debian-like systems, you can install them with apt-get install mono-mcs gcc-mingw-w64-x86-64 gcc-mingw-w64-i686.

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: