https://github.com/secdec/attack-surface-detector-zap

The Attack Surface Detector uses static code analyses to identify web app endpoints by parsing routes and identifying parameters
https://github.com/secdec/attack-surface-detector-zap

dast pentesting security vulnerability

Last synced: 17 days ago
JSON representation

The Attack Surface Detector uses static code analyses to identify web app endpoints by parsing routes and identifying parameters

• Host: GitHub
• URL: https://github.com/secdec/attack-surface-detector-zap
• Owner: secdec
• License: mpl-2.0
• Created: 2018-03-30T15:20:50.000Z (over 6 years ago)
• Default Branch: master
• Last Pushed: 2023-04-11T10:02:18.000Z (over 1 year ago)
• Last Synced: 2024-04-16T12:21:47.514Z (3 months ago)
• Topics: dast, pentesting, security, vulnerability
• Language: Java
• Homepage:
• Size: 15.7 MB
• Stars: 59
• Watchers: 11
• Forks: 14
• Open Issues: 5
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Lists

• WebHackersWeapons - attack-surface-detector-zap - surface-detector-zap?label=%20)|[`endpoint`](/categorize/tags/endpoint.md) [`url`](/categorize/tags/url.md) [`attack-surface`](/categorize/tags/attack-surface.md)|[](/categorize/langs/Java.md)| (Weapons / Burpsuite and ZAP Addons)

README

        
![asd-logo](https://user-images.githubusercontent.com/35819157/41377213-60ca05de-6f29-11e8-8c05-e29720906c90.png)

# Summary

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.

# How it Works

The Attack Surface Detector uses static code analyses to identify web app endpoints by parsing routes and identifying parameters (with supported languages and frameworks).

## Supported Frameworks:

  * C# / ASP.NET MVC

  * C# / Web Forms

  * Java / Spring MVC

  * Java / Struts

  * Java JSP

  * Python / Django

  * Ruby / Rails

To see a brief demonstration for the Attack Surface Detector, you can check it out [here:](https://youtu.be/jUUJNRcmqwI) *Note: this demonstration is based on the plugin built for Portswigger's Burp Suite. Implementation and operations are nearly identical for the ZAP plugin.*

## Installing the Plugin

1. [Detailed install instructions](https://github.com/secdec/attack-surface-detector-zap/wiki/Installation).

# For Developers & Contributors

## Build Instructions

1.  Install Maven. - [https://maven.apache.org/install.html](https://maven.apache.org/install.html)

2. Clone Attack Surface Detector repository - https://github.com/secdec/attack-surface-detector-zap 

3. Navigate to the Source Code Directory

4. Open a new terminal and run the command `mvn clean package`

4. The plugin will be located in the target folder named attacksurfacedetector-release-#.zap

## License

Licensed under the [MPL](https://github.com/secdec/attack-surface-detector-zap/blob/master/LICENSE) License.