heartbleed-weaponized | A collection of different Heartbleed | Security Testing library

by johnmarkschofield Python Version: Current License: MIT

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

kandi X-RAY | heartbleed-weaponized Summary

heartbleed-weaponized is a Python library typically used in Testing, Security Testing applications. heartbleed-weaponized has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. However heartbleed-weaponized build file is not available. You can download it from GitHub.

The Heartbleed bug was released on April 7, 2014. Shortly thereafter, a raft of checkers and testers emerged, starting with ilippo.io/Heartbleed/. That is a website that checks submitted sites for vulnerability to the Heartbleed OpenSSL bug. More and more checking tools have been released since that one, including possible.lv/tools/hb/. It is important for Systems Operations people to be able to check their servers without submitting their server addresses to a public website. That's somewhat like submitting your password to a public website to check if the password is a good one. Probably not a good idea, even if the website is above-board. This Vagrant virtualmachine contains tools you can use to verify whether or not your website, and websites that you use, such as your bank and email provider, are vulnerable to the Heartbleed bug. It will not contain tools to exploit the Heartbleed vulnerability, although such tools already exist. The intent of this repo is make the jobs of people protecting the web easier, not to make attacker's jobs easier. You can be sure, however, that people are out there working hard to make attackers jobs easier.

Support

Quality

Security

License

Reuse

Support

heartbleed-weaponized has a low active ecosystem.

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

It had no major release in the last 6 months.

heartbleed-weaponized has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of heartbleed-weaponized is current.

Quality

heartbleed-weaponized has no bugs reported.

Security

heartbleed-weaponized has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

heartbleed-weaponized 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

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

heartbleed-weaponized has no build file. You will be need to create the build yourself to build the component from source.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

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

Start the server .
Check if a heartbeat failed .
Recieve data from a stream .
Read a message from a string .
Pretty print a hexadecimal string
Convert x to binary string .

Get all kandi verified functions for this library.

heartbleed-weaponized Key Features

No Key Features are available at this moment for heartbleed-weaponized.

heartbleed-weaponized Examples and Code Snippets

No Code Snippets are available at this moment for heartbleed-weaponized.

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 heartbleed-weaponized

If you have the latest version of VirtualBox installed, and you have vagrant-vbguest installed you'll need to do:.

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: