attack-surface-detector-zap | Attack Surface Detector uses static code analyses | Security Testing library

 by   secdec Java Version: 1.1.4 License: MPL-2.0

kandi X-RAY | attack-surface-detector-zap Summary

kandi X-RAY | attack-surface-detector-zap Summary

attack-surface-detector-zap is a Java library typically used in Testing, Security Testing applications. attack-surface-detector-zap has no vulnerabilities, it has build file available, it has a Weak Copyleft License and it has low support. However attack-surface-detector-zap has 6 bugs. You can download it from GitHub.

During web application penetration testing, it is important to enumerate your application's attack surface. While Dynamic Application Security Testing (DAST) tools (such as Burp Suite and ZAP) are good at spidering to identify application attack surfaces, they will often fail to identify unlinked endpoints and optional parameters. These endpoints and parameters not found often go untested, which can leave your application open to an attacker. This tool is the Attack Surface Detector, a plugin for OWASP ZAP. This tool figures out the endpoints of a web application, the parameters these endpoints accept, and the data type of those parameters. This includes the unlinked endpoints a spider won't find in client-side code, or optional parameters totally unused in client-side code. The plugin then imports this data into ZAP so you view the results, or work with the detected endpoints and parameters from the target site map.
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              attack-surface-detector-zap has a low active ecosystem.
              It has 55 star(s) with 12 fork(s). There are 11 watchers for this library.
              OutlinedDot
              It had no major release in the last 12 months.
              There are 4 open issues and 9 have been closed. On average issues are closed in 14 days. There are no pull requests.
              It has a neutral sentiment in the developer community.
              The latest version of attack-surface-detector-zap is 1.1.4

            kandi-Quality Quality

              OutlinedDot
              attack-surface-detector-zap has 6 bugs (1 blocker, 0 critical, 3 major, 2 minor) and 217 code smells.

            kandi-Security Security

              attack-surface-detector-zap has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              attack-surface-detector-zap code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              attack-surface-detector-zap is licensed under the MPL-2.0 License. This license is Weak Copyleft.
              Weak Copyleft licenses have some restrictions, but you can use them in commercial projects.

            kandi-Reuse Reuse

              attack-surface-detector-zap releases are available to install and integrate.
              Build file is available. You can build the component from source.
              Installation instructions are available. Examples and code snippets are not available.
              attack-surface-detector-zap saves you 1764 person hours of effort in developing the same functionality from scratch.
              It has 3902 lines of code, 138 functions and 15 files.
              It has high code complexity. Code complexity directly impacts maintainability of the code.

            Top functions reviewed by kandi - BETA

            kandi has reviewed attack-surface-detector-zap and discovered the below as its top functions. This is intended to give you an instant insight into attack-surface-detector-zap implemented functionality, and help decide if they suit your requirements.
            • Initialize the panel
            • Add the endpoints table
            • Build the help panel
            • Build the options panel
            • Runs the analysis
            • Get the node for the specified URL
            • Sends a HttpMessage and processes it
            • Start the spider
            • Authenticates the URL for the given URL
            • Start the attack thread
            • Compare two endpoints
            • Returns the hashcode of the request
            • If the maximum length is greater than maxLength then remove maxLength
            • Sets key and url
            • Retrieves the list of endpoints from a file
            • Builds the nodes from the endpoints
            • Replaces the specified text within the specified range of characters
            • Overrides the superclass method
            • Adds the endpoints to the table model
            • Get list of endpoints from source folder
            • Sets a new property value
            Get all kandi verified functions for this library.

            attack-surface-detector-zap Key Features

            No Key Features are available at this moment for attack-surface-detector-zap.

            attack-surface-detector-zap Examples and Code Snippets

            No Code Snippets are available at this moment for attack-surface-detector-zap.

            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 attack-surface-detector-zap

            Install Maven. - https://maven.apache.org/install.html
            Clone Attack Surface Detector repository - https://github.com/secdec/attack-surface-detector-zap
            Navigate to the Source Code Directory
            Open a new terminal and run the command mvn clean package
            The plugin will be located in the target folder named attacksurfacedetector-release-#.zap

            Support

            To see a brief demonstration for the Attack Surface Detector, you can check it out here: Note: this demonstration is based on the plugin built for Portswigger's Burp Suite. Implementation and operations are nearly identical for the ZAP plugin.
            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/secdec/attack-surface-detector-zap.git

          • CLI

            gh repo clone secdec/attack-surface-detector-zap

          • sshUrl

            git@github.com:secdec/attack-surface-detector-zap.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 secdec

            adapt

            by secdecPython

            xssmap

            by secdecPython

            pen-test-automation

            by secdecJava