How atomiczsec/web-cache-deception-scanner-main works
Project type and purpose
• This is a Java-based Burp Suite extension (plugin) named “Web Cache Deception Scanner” for the Burp Suite Community Edition.
• Its purpose is to hook into Burp’s UI, add a context-menu command, and automate a series of HTTP tests against target endpoints to detect web cache deception vulnerabilities.
File structure
• Top-level build files:
• build.gradle, settings.gradle, Gradle wrapper scripts under gradle/
• Source code under src/main/java/burp/:
• BurpExtender.java – the entry point that implements Burp’s IBurpExtender and IContextMenuFactory interfaces
• RequestSender.java – encapsulates all HTTP request/response logic (initial mapping, delimiter tests, path-normalization tests)
• WebCacheIssue.java – models and reports discovered cache deception issues back into Burp’s UI
Key insights from README
• The extension registers a right-click menu item in Burp’s Target and Proxy tabs.
• When invoked, it performs three main test phases (path-mapping, extension-delimiter, normalization).
• Built with Gradle, outputs a “-all.jar” plugin loaded into Burp.
Main components and relationships
a. Components
• Burp Suite Host (UI & core API)
• Extension JAR (web-cache-deception-scanner-all.jar)
• BurpExtender (entry point)
• RequestSender (HTTP logic module)
• WebCacheIssue (reporting/data model)
• Target Web Application (external HTTP service)
b. Interactions
1. At load time, Burp Suite invokes BurpExtender.registerExtenderCallbacks()
2. BurpExtender registers itself as a context-menu factory
3. User right-clicks a request → Burp invokes BurpExtender.createMenuItems()
4. User selects “Web Cache Deception Test” → extension calls RequestSender to run tests in sequence
5. RequestSender issues authenticated and unauthenticated HTTP requests to the Target Web Application
6. Responses come back and are compared for similarity
7. If a vulnerability is detected, WebCacheIssue instances are created and passed back via callbacks to display in Burp’s Scanner/Issue panel
c. Architectural patterns and principles
• Plugin architecture: Implements Burp’s extension API interfaces to decouple from Burp’s core
• Single Responsibility Classes:
• BurpExtender handles registration and menu wiring
• RequestSender handles all HTTP/test logic
• WebCacheIssue encapsulates data and reporting
d. Relevant technologies/frameworks
• Java 11+
• Burp Suite Extension API (IBurpExtender, IContextMenuFactory, IHttpRequestResponse, IScanIssue)
• Gradle build system
Detail
• Test phase as a sub-component or note in RequestSender (Initial Path Mapping, Delimiter+Extension Test, Path Normalization Test)
• Build artifact generation via Gradle (optional small side-note)