How portswigger/httpoxy-scanner works
Project type and purpose
• This is a sample Burp Suite extension that demonstrates use of the HTTPoxy vulnerability with the Burp Collaborator service.
• It provides three language implementations (Java, Python, Ruby) as Burp extensions and a simple Node.js server to simulate a vulnerable application.
File structure
• Top‑level artifacts:
• BappDescription.html, BappManifest.bmf – metadata for packaging as a Burp extension (BApp).
• README.md – overview, architecture hints, usage instructions.
• java/ – Java Gradle project with BurpExtender.java and HttPoxyIssue.java.
• python/ – Python implementation of the same logic.
• ruby/ – Ruby implementation.
• server/server.js – simple Node.js HTTP server that reads Proxy headers and makes outgoing requests to the Collaborator URL.
• Notices:
• Three parallel implementation folders share the same high‑level logic: generate collaborator payloads, trigger test requests, retrieve interactions.
• A standalone server folder serves as the vulnerable target for active scanning.
README for additional insights
• The extension:
• Uses Burp Collaborator context to generate unique payload URLs.
• Injects these URLs into Proxy headers during an active scan.
• Polls the Collaborator for any inbound interactions, detecting an HTTPoxy condition.
• The provided server merely issues HTTP requests to any URL found in incoming Proxy headers.