Slackor | Golang implant that uses Slack | Security Testing library

by Coalfire-Research Python Version: Current License: GPL-3.0

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

kandi X-RAY | Slackor Summary

Slackor is a Python library typically used in Testing, Security Testing applications. Slackor has build file available, it has a Strong Copyleft License and it has low support. However Slackor has 53 bugs and it has 103 vulnerabilities. You can download it from GitHub.

A Golang implant that uses Slack as a command and control channel. This project was inspired by [Gcat] and [Twittor] ![Slackor Screenshot] ![Wireshark Screenshot] This tool is released as a proof of concept. Be sure to read and understand the [Slack App Developer Policy] before creating any Slack apps.

Support

Quality

Security

License

Reuse

Support

Slackor has a low active ecosystem.

It has 439 star(s) with 105 fork(s). There are 16 watchers for this library.

It had no major release in the last 6 months.

There are 4 open issues and 3 have been closed. On average issues are closed in 2 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of Slackor is current.

Quality

Slackor has 53 bugs (11 blocker, 0 critical, 37 major, 5 minor) and 10767 code smells.

Security

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

Slackor code analysis shows 103 unresolved vulnerabilities (30 blocker, 64 critical, 7 major, 2 minor).

There are 266 security hotspots that need review.

License

Slackor 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

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

Top functions reviewed by kandi - BETA

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

Parse a TDS data row .
Process a session setup .
Create a Kerberos TGT .
Performs a S4U response .
Decrypts the HMAC hash .
Implements the SMB session setup .
Build a PAC data structure .
Creates a key for the given ticket .
Respond to SMB session setup .
Handle a SMB2 SessionSetup response

Get all kandi verified functions for this library.

Slackor Key Features

No Key Features are available at this moment for Slackor.

Slackor Examples and Code Snippets

No Code Snippets are available at this moment for Slackor.

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 Slackor

For this to work you need: - A Slack Workspace - [Register an app](https://api.slack.com/apps) with the following permissions: - channels:read - channels:history - channels:write - files:write:user - files:read. This repo contains five files: - install.sh Installs dependancies - setup.py The script to create the slack channels, database, and implant - agent.py Script to generate new implants - server.py The Slackor server, designed to be ran on Linux - agent.go The golang implant - requirements.txt Python dependencies (installed automatically). After running the script successfully, several files will be created in the dist/ directory: - agent.windows.exe: Windows 64-bit binary - agent.upx.exe: Windows 64-bit binary, UPX packed - agent.darwin: macOS 64-bit binary - agent.32.linux: Linux 32-bit binary - agent.64.linux: Linux 64-bit binary. After starting server.py on a Linux host, execute whichever agent above is appropriate for your target host. Run the "stager" module to generate a one-liner and other droppers. This will execute InvokeWebRequest(PS v.3+) to download the payload, execute it using a [LOLBin](https://lolbas-project.github.io/lolbas/Binaries/Forfiles/), and then delete itself once killed. This is a working example but the command can tweaked to use another download method or execution method.
Create a bot
go get github.com/Coalfire-Research/Slackor
cd $GOPATH/src/github.com/Coalfire-Research/Slackor
Run install.sh
Run setup.py
Supply the OAuth Access Token and Bot User OAuth Access Token from your app

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: