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
noorqureshi/web-cache-poisoningWeb and bug bounty

web-cache-poisoning

⁨Web cache poisoning & deception — get a shared cache to serve attacker content to other users, or trick it into caching victims' private pages. Load behind a CDN/cache (Cloudflare, Varnish, Fastly, Akamai), on unkeyed headers, `X-Forwarded-Host`, cache headers, or static-looking URLs. Signals: `Age`⁩

v2026.10.14-ee0e0c55 installs+5 in 7 days27 StarsMITsynced 22 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/web-cache-poisoning

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

SignatureSigned, ed25519
gbCle2ZoCA…OsHezdCA==The CLI checks the SHA-256 and the signature before it writes a file.
Package7a3c0fb5…63ed9fe8
7a3c0fb5d034…cf2163ed9fe81 file · ⁦1.4 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/web/web-cache-poisoning@ee0e0c5

When it applies

A shared cache (CDN/reverse proxy) sits in front of the app. Poisoning: an unkeyed input influences the response but isn't part of the cache key, so your malicious response gets stored and served to everyone. Deception: the cache is tricked into storing a victim's private page.

Why it works

Caches key on some request parts (URL, maybe some headers) and ignore others ("unkeyed"). If an unkeyed header/param changes the response (reflected X-Forwarded-Host, a header-driven script src), you poison the cached copy. Deception exploits path/extension rules that cache things that shouldn't be cached.

Method

  1. Map cache behaviour: X-Cache: hit/miss, Age, Cache-Control, CDN vendor. Send a cache-buster param to test safely without poisoning the real key.
  2. Find unkeyed inputs with Burp Param Miner ("guess headers"): X-Forwarded-Host, X-Forwarded-Scheme, X-Host, custom headers reflected into the response.
  3. Poison (carefully): make the unkeyed input inject a payload (e.g. X-Forwarded-Host: evil.com → a script/link src) that reflects into a cacheable response; confirm it's stored and served to a clean request.
  4. Deception: request /account.php/nonexistent.css — if the cache stores the private page under the static-looking URL, another user can fetch victims' cached data.

Gotchas

  • Test with a unique cache-buster so you don't poison production for real users; then prove one controlled hit.
  • Impact = what the poisoned response does (XSS, redirect, defacement) × who receives it.
  • CDNs normalize/strip headers differently — the win is a specific input this cache doesn't key on.

Verify success

A clean request (no attacker input) receives your poisoned response, or a victim's private page is served from cache to you.

References

James Kettle "Practical Web Cache Poisoning"; PortSwigger cache labs; Param Miner.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

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

VersionPublishedCommitSHA-256SignaturePermission change
v2026.10.14-ee0e0c5Nov 13, 2026ee0e0c57a3c0fb5Signed–

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