Salsa-tools | Salsa Tools - ShellReverse TCP | Security Testing library

by Hackplayers C# Version: Current License: GPL-3.0

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

kandi X-RAY | Salsa-tools Summary

Salsa-tools is a C# library typically used in Testing, Security Testing applications. Salsa-tools has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. You can download it from GitHub.

Salsa-Tools is made from three different ingredients: - EvilSalsa - EncrypterAssembly - SalseoLoader And his behavior is as it follows:.

Support

Quality

Security

License

Reuse

Support

Salsa-tools has a low active ecosystem.

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

It had no major release in the last 6 months.

There are 0 open issues and 5 have been closed. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of Salsa-tools is current.

Quality

Salsa-tools has 0 bugs and 0 code smells.

Security

Salsa-tools has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

Salsa-tools code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

Salsa-tools 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

Salsa-tools releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Salsa-tools saves you 220 person hours of effort in developing the same functionality from scratch.

It has 538 lines of code, 29 functions and 17 files.

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

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of Salsa-tools

Get all kandi verified functions for this library.

Salsa-tools Key Features

No Key Features are available at this moment for Salsa-tools.

Salsa-tools Examples and Code Snippets

No Code Snippets are available at this moment for Salsa-tools.

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 Salsa-tools

Download the source code from the github and compile EvilSalsa and SalseoLoader. You will need Visual Studio installed to compile the code. Compile those projects for the architecture of the windows box where your are going to use them(If the Windows supports x64 compile them for that architectures). You can select the architecture inside Visual Studio in the left "Build" Tab in "Platform Target". (If you can't find this options press in "Project Tab" and then in " Properties").
In your project folder have appeared the files: DllExport.bat and DllExport_Configure.bat.
Select Output Type = Class Library (Project --> SalseoLoader Properties --> Application --> Output type = Class Library). Select x64 platform (Project --> SalseoLoader Properties --> Build --> Platform target = x64). To build the solution: Build --> Build Solution (Inside the Output console the path of the new DLL will appear).

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: