Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
crlf-powered-desync-scanner — Burp extension scanner for CRLF injection and HTTP desync attacks, using mutated probes, WAF false-positive checks, and optional response-queue-poisoning auto-exploitation. | Kitploit
Tools/GitHubGitHub/t0xodile/crlf-powered-desync-scanner
Web Vulnerability ScannersExploitationWeb Application ExploitationWeb SecurityPenetration Testing
GitHubt0xodile/crlf-powered-desync-scanner

crlf-powered-desync-scanner

Burp extension scanner for CRLF injection and HTTP desync attacks, using mutated probes, WAF false-positive checks, and optional response-queue-poisoning auto-exploitation.

View Repository
14624 months agoReviewed by Kitploit
Share

CRLF-Powered Desync Scanner

This is the Burp Extension we used to detect all cases from our research CRLF-Powered Desync Attacks: Beheading HTTP Streams.

It's a research-first scanner built using BulkScan similar to HTTP Request Smuggler and others.

Implementation

Request Header Injection probe

Uses all the defined mutations in src/main/kotlin/ReqMutator to fire a benign and then probe request. If the response contains an expected match, or differs significantly, an issue is reported.

If the response contained all expected matches, then the issue is reported as normal. If the fallback diff is enabled (uses serverStatus from BulkScan) then the issue is reported as Dodgy.

There is also a WAFChecker which uses static strings to try and reduce FPs from WAF rules and follow-up logic that ensures the behaviour is consistent or at least most likely not a WAF rule that isn't in the WAFChecker list already. Additionally, there is an "auto-exploit via Response Queue Poisoning" button that may or may not give you a clue that RQP works out of the box.

Response Header Injection probe

Injects a header containing a random canary into the request path and checks whether that header is reflected back in the response headers. If it is, the injection is confirmed and an issue is reported.

As a follow-up, it then injects a Content-Length header to see if the response can be split. If this causes a timeout or a change in the serverStatus, the issue is upgraded and reported as Splitting?.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    933
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    551
  • 3

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    354
  • 4

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    351
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    332
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    289

Explore all tools

Browse our collection of tools

View all tools →