CVE-2018-1000802-PoC | Python CVE-2018-1000802 Proof-of-Concept | Security Testing library

 by   tna0y Python Version: Current License: No License

kandi X-RAY | CVE-2018-1000802-PoC Summary

kandi X-RAY | CVE-2018-1000802-PoC Summary

CVE-2018-1000802-PoC is a Python library typically used in Testing, Security Testing applications. CVE-2018-1000802-PoC has no bugs, it has no vulnerabilities and it has low support. However CVE-2018-1000802-PoC build file is not available. You can download it from GitHub.

Python CVE-2018-1000802 Proof-of-Concept
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              CVE-2018-1000802-PoC has a low active ecosystem.
              It has 4 star(s) with 0 fork(s). There are no watchers for this library.
              OutlinedDot
              It had no major release in the last 6 months.
              CVE-2018-1000802-PoC has no issues reported. There are no pull requests.
              It has a neutral sentiment in the developer community.
              The latest version of CVE-2018-1000802-PoC is current.

            kandi-Quality Quality

              CVE-2018-1000802-PoC has no bugs reported.

            kandi-Security Security

              CVE-2018-1000802-PoC has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

            kandi-License License

              CVE-2018-1000802-PoC does not have a standard license declared.
              Check the repository for any license declaration and review the terms closely.
              OutlinedDot
              Without a license, all rights are reserved, and you cannot use the library in your applications.

            kandi-Reuse Reuse

              CVE-2018-1000802-PoC releases are not available. You will need to build from source code and install.
              CVE-2018-1000802-PoC has no build file. You will be need to create the build yourself to build the component from source.

            Top functions reviewed by kandi - BETA

            kandi has reviewed CVE-2018-1000802-PoC and discovered the below as its top functions. This is intended to give you an instant insight into CVE-2018-1000802-PoC implemented functionality, and help decide if they suit your requirements.
            • Makes the information available in the system .
            • Creates a denial of service .
            • Generate arguments .
            Get all kandi verified functions for this library.

            CVE-2018-1000802-PoC Key Features

            No Key Features are available at this moment for CVE-2018-1000802-PoC.

            CVE-2018-1000802-PoC Examples and Code Snippets

            No Code Snippets are available at this moment for CVE-2018-1000802-PoC.

            Community Discussions

            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-2018-1000802-PoC

            You can download it from GitHub.
            You can use CVE-2018-1000802-PoC like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

            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:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
            CLONE
          • HTTPS

            https://github.com/tna0y/CVE-2018-1000802-PoC.git

          • CLI

            gh repo clone tna0y/CVE-2018-1000802-PoC

          • sshUrl

            git@github.com:tna0y/CVE-2018-1000802-PoC.git

          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link

            Explore Related Topics

            Consider Popular Security Testing Libraries

            PayloadsAllTheThings

            by swisskyrepo

            sqlmap

            by sqlmapproject

            h4cker

            by The-Art-of-Hacking

            vuls

            by future-architect

            PowerSploit

            by PowerShellMafia

            Try Top Libraries by tna0y

            fastchan

            by tna0yGo

            VonNeumannVM

            by tna0yPython

            dataengineer4_lab1

            by tna0yPython