GoCookies | A browser cookie stealer | Security Testing library

by simonfalke-01 Go Version: v0.0.1 License: GPL-3.0

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

kandi X-RAY | GoCookies Summary

GoCookies is a Go library typically used in Testing, Security Testing applications. GoCookies has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. You can download it from GitHub.

GoCookies is a tool for stealing cookies from a victim's browser and sending them to an attacker's machine. It is written in Go and has three components: gocookies, gocookies-generate, and gocookies-listener. The gocookies-generate component generates a payload that can be sent to the victim. This payload steals the cookies from the victim's browser and sends them to the gocookies-listener component running on the attacker's machine. The gocookies-listener component receives the cookies and stores them in a Redis database running in a Docker container.

Support

Quality

Security

License

Reuse

Support

GoCookies has a low active ecosystem.

It has 3 star(s) with 0 fork(s). There are 1 watchers for this library.

It had no major release in the last 12 months.

GoCookies has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of GoCookies is v0.0.1

Quality

GoCookies has no bugs reported.

Security

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

License

GoCookies 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

GoCookies releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

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 GoCookies

Get all kandi verified functions for this library.

GoCookies Key Features

No Key Features are available at this moment for GoCookies.

GoCookies Examples and Code Snippets

No Code Snippets are available at this moment for GoCookies.

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 GoCookies

To get started with GoCookies, follow these steps:. For Windows: Idk if it even works. Alternatively, you can download the binaries manually from the releases page.
Clone the repository:
Download the latest release:
Before running the listener, ensure that the docker daemon is running. Then, pull the redis image:.
-r - The port on which Redis will be running.
-p - The port on which the listener will be running.
-e (optional) - Whether to use an existing Redis container (if not specified, a new Redis container will be created). If specified, -r will be the port of the existing Redis container.

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: