Firmware_Slap | Discovering vulnerabilities in firmware through concolic | Security Testing library

by ChrisTheCoolHut Python Version: Current License: GPL-3.0

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

kandi X-RAY | Firmware_Slap Summary

Firmware_Slap is a Python library typically used in Testing, Security Testing applications. Firmware_Slap 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 download it from GitHub.

Discovering vulnerabilities in firmware through concolic analysis and function clustering.

Support

Quality

Security

License

Reuse

Support

Firmware_Slap has a low active ecosystem.

It has 453 star(s) with 80 fork(s). There are 12 watchers for this library.

It had no major release in the last 6 months.

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

It has a neutral sentiment in the developer community.

The latest version of Firmware_Slap is current.

Quality

Firmware_Slap has 0 bugs and 0 code smells.

Security

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

Firmware_Slap code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

Firmware_Slap 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

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

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

Installation instructions, examples and code snippets are available.

Firmware_Slap saves you 1092 person hours of effort in developing the same functionality from scratch.

It has 2473 lines of code, 124 functions and 21 files.

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

Top functions reviewed by kandi - BETA

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

Get vulnerabilities from a list of functions
Prints a function to stdout
Get vulnerabilities from functions
Fixes index_funcs
Check for bug issues
Get the next item from the queue
Print a function to stdout
Makes pickleable object
Get information about a Parameter
Returns a dictionary of all the attributes of a variable
Get information about a variable
Test the command line
Unravel a pointer
Performs a single clustering
Performs clustering
Dump the results to a JSON file
Helper function to parallelize multiple functions
Get the arguments of the function
Execute an async function and return the results
Display corruption location
Create index by name
Pretty print a value
Check if all files in task_list exist
Asynchronously trace a function
Unravels a pointer
Stop running docker container
Process a file or folder
Return an item from the queue
Return a list of function names

Get all kandi verified functions for this library.

Firmware_Slap Key Features

No Key Features are available at this moment for Firmware_Slap.

Firmware_Slap Examples and Code Snippets

No Code Snippets are available at this moment for Firmware_Slap.

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 Firmware_Slap

Firmware slap should be run in a virtual environment. It has been tested on Python3.6. You will need rabbitmq, docker, and (radare2 or Ghidra). Ghidra requires JDK 11. If you want to use the Elastic search stuff run the Elasticsearch_and_kibana.sh script.
Ensure rabbitmq-server is running.

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: