CVE-2020-1472 | Test tool for CVE-2020-1472 | Security Testing library

by SecuraBV Python Version: Current License: MIT

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

kandi X-RAY | CVE-2020-1472 Summary

CVE-2020-1472 is a Python library typically used in Testing, Security Testing applications. CVE-2020-1472 has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has medium support. You can download it from GitHub.

Test tool for CVE-2020-1472

Support

Quality

Security

License

Reuse

Support

CVE-2020-1472 has a medium active ecosystem.

It has 1562 star(s) with 353 fork(s). There are 89 watchers for this library.

It had no major release in the last 6 months.

There are 6 open issues and 20 have been closed. On average issues are closed in 42 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of CVE-2020-1472 is current.

Quality

CVE-2020-1472 has 0 bugs and 2 code smells.

Security

CVE-2020-1472 has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

CVE-2020-1472 code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

CVE-2020-1472 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

CVE-2020-1472 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.

CVE-2020-1472 saves you 21 person hours of effort in developing the same functionality from scratch.

It has 59 lines of code, 3 functions and 1 files.

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

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 CVE-2020-1472

Get all kandi verified functions for this library.

CVE-2020-1472 Key Features

No Key Features are available at this moment for CVE-2020-1472.

CVE-2020-1472 Examples and Code Snippets

Execution

Python

Lines of Code : 17

License : Permissive (MIT)

Copy

usage: zerologon_test.py [-h] [-u] [-d] [-p] [-t] [-pp] dc_name dc_ip

Perform zerologon test over RPC/TCP or RPC/SMB

positional arguments:
  dc_name               NetBIOS name of the domain controller
  dc_ip                 ip address of the domai

CVE-2020-1472 POC,Environment

Python

Lines of Code : 5

License : No License

Copy

vim  /Users/xq17/.proxychains/proxychains.conf

1.git clone https://github.com/mstxq17/cve-2020-1472.git
2.pip3 install -r requirements.txt

git clone https://github.com/SecureAuthCorp/impacket.git
cd impacket && pip3 install .

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 CVE-2020-1472

Requires Python 3.7 or higher and Pip. Install dependencies as follows:. Note that running pip install impacket should work as well, as long as the script is not broken by future Impacket versions.

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: