commix | Automated All-in-One OS Command Injection Exploitation Tool | Security Testing library

by commixproject Python Version: v3.7 License: Non-SPDX

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

kandi X-RAY | commix Summary

commix is a Python library typically used in Testing, Security Testing applications. commix has no vulnerabilities, it has build file available and it has medium support. However commix has 33 bugs and it has a Non-SPDX License. You can download it from GitHub.

Commix (short for [comm]and [i]njection e[x]ploiter) is an open source penetration testing tool, written by Anastasios Stasinopoulos (@ancst), that automates the detection and exploitation of command injection vulnerabilities.

Support

Quality

Security

License

Reuse

Support

commix has a medium active ecosystem.

It has 3872 star(s) with 760 fork(s). There are 152 watchers for this library.

It had no major release in the last 12 months.

There are 5 open issues and 807 have been closed. On average issues are closed in 57 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of commix is v3.7

Quality

commix has 33 bugs (6 blocker, 0 critical, 3 major, 24 minor) and 1157 code smells.

Security

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

commix code analysis shows 0 unresolved vulnerabilities.

There are 28 security hotspots that need review.

License

commix has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

commix 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.

commix saves you 11139 person hours of effort in developing the same functionality from scratch.

It has 22567 lines of code, 736 functions and 111 files.

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

Top functions reviewed by kandi - BETA

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

Implementation of Powershell
Insert a new child element at position
Create a new instance
Return the last child of this node
Estimate the time of the target URL
Return the value of the attribute key
Returns a dictionary containing the attrMap
Check HTTP traffic
Print HTTP response
Configures the reverse transport
Check for custom injection marker
Return the encoding of the XML data
Checks a cookie
Perform HTTP authentication
Run crawler
Extract injection results from HTML response
Read a single input
Configures the TCP connection
Unhandled exceptions
Start the installer
Do the check
Checks whether a given command is true
Perform HTTP POST check
Print a list of user names
Parse logfile
Perform a GET check on the provided URL

Get all kandi verified functions for this library.

commix Key Features

No Key Features are available at this moment for commix.

commix Examples and Code Snippets

PoC,Commix Test Bed

Python

Lines of Code : 109

License : Strong Copyleft (GPL-3.0)

Copy

Classic regular example
python3 CIExtender.py -u http://www.local.con/commix-testbed/scenarios/regular/GET/classic.php?addr=* -v1 --flush-session

Classic (Base64) regular example
(default sqlmap tamper script)
python3 CIExtender.py -u http://www.loc

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