Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤖 Automated Content Update
This PR was automatically generated by the HackTricks News Bot based on a technical blog post.
📝 Source Information
🎯 Content Summary
Topic / goal
The post is a hands-on guide to connect Burp Suite traffic to an LLM “reasoning client” (Codex CLI) via the Burp Suite MCP Server extension (from the BApp Store). The intent is to let the LLM reason over real intercepted HTTP requests/responses (Burp evidence) for passive vulnerability discovery and report writing, without API keys, scanning, or fuzzing.
What you get (outcomes)
• Passive vuln discovery based on observ...
🔧 Technical Details
LLM reasoning directly on Burp-captured HTTP via MCP stdio bridge: Run Burp’s MCP Server extension and extract the “server proxy jar”. Configure an MCP client (Codex CLI) to launch that jar and speak MCP over stdio; the jar bridges to Burp MCP, enabling programmatic querying/reasoning over intercepted requests/responses for passive bug discovery and evidence-based reporting.
Fix strict-Origin/extra-header MCP handshake failures with a reverse proxy: If an MCP server rejects the client handshake due to strict
Originvalidation or unexpected headers, place a local reverse proxy (e.g., Caddy) in front of the MCP endpoint to normalize/forward requests so the handshake succeeds while keeping analysis local.Attribution and traffic tracking using proxy header rewriting: Use regex-based header rewrite rules at the proxy layer to tag traffic (e.g., match
^User-Agent: (.*)$and replace withUser-Agent: $1 BugBounty-Username🤖 Agent ActionsSummary:Testing:
This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.