When a Web App Detects Burp Suite via TLS Fingerprinting - #2647
Open
carlospolop wants to merge 1 commit into
Open
When a Web App Detects Burp Suite via TLS Fingerprinting#2647carlospolop wants to merge 1 commit into
carlospolop wants to merge 1 commit into
Conversation
Collaborator
Author
🔗 Additional ContextOriginal Blog Post: https://kecman.co/blog/burp-suite-tls-fingerprint-bot-detection-bypass.html Content Categories: Based on the analysis, this content was categorized under "Pentesting Web > Proxy / WAF Protections Bypass > TLS, JA3/JA4, and HTTP/2 Fingerprint Evasion with Burp Suite". Repository Maintenance:
Review Notes:
Bot Version: HackTricks News Bot v1.0 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Overview
The post explains how bot-management systems can detect traffic intercepted by Burp Suite by comparing the browser identity claimed at the HTTP layer with the TLS and HTTP/2 fingerprints observed on the connection. This is not an application vulnerability: it is a defensive anti-automation capability and a potential testing artifact. During an authorized assessment, however, modifying Burp's outbound fingerprint can prevent bot scoring from silently rejecting proxied requests...
🔧 Technical Details
Detecting proxy/header inconsistencies: A TLS-intercepting proxy creates independent client-facing and server-facing TLS sessions. The destination sees HTTP headers copied from the browser but fingerprints the proxy's own outbound
ClientHello. Comparing the claimed browser identity with JA3/JA4, cipher and extension ordering, ALPN, HTTP/2SETTINGS, pseudo-header ordering, header ordering, and handshake timing can identify interception or automation even when the HTTP request itself appears browser-generated.Shaping a proxy's outbound TLS fingerprint: Reconfigure the server-facing TLS stack to advertise a short, modern, browser-like cipher list instead of a large library-default list containing legacy suites. In Burp, right-click the scoped host and use Extensions → Bypass Bot Detection → Adjust ciphers to common browsers. This modifies connection #2 and can improve risk-based bot score...
🤖 Agent Actions
Updated
src/pentesting-web/proxy-waf-protections-bypass.mdwith:Validation:
git diff --checkpassed.mdbook buildwas unavailable becausemdbookis not installed.This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.