web-cache-deception
Trick a CDN/cache into storing a victim's authenticated response at a public URL, then read it. Load on "web cache deception", when a CDN/cache sits in front of an app that serves per-user content, or to test whether private pages can be cached. Signals: `X-Cache`/`CF-Cache-Status` headers, caching
v2026.10.14-ee0e0c55 installazioni+5 in 7 giorni27 StelleMITsincronizzato 22 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/web-cache-deceptionScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto56470805…9adc140b
564708054e06…8f2b9adc140b1 file · 1.4 KBScansioneBassonessuna segnalazione
Sorgentegithub.com/NoorQureshi/security-skills/tree/main/skills/web/web-cache-deception@ee0e0c5
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
When it applies
A caching layer (CDN, reverse proxy) fronts an app that returns per-user content, and the cache decides what to store by URL pattern/extension. If you can make an authenticated response look cacheable, the cache stores it — and anyone can then fetch that victim's data.
Why it works
The cache and the origin disagree about the URL. The cache sees /account.css and thinks "static,
cache it"; the origin ignores the .css suffix (or a delimiter) and serves the dynamic
/account page. The victim's private response gets stored under a public key you can request.
Method
- Confirm the mismatch: request an authenticated page with a static suffix —
/account/foo.css,/account%0a.css,/account;foo.js,/account%2ffoo.css. If the origin still returns the account page (not 404), the origin is ignoring the suffix. - Confirm caching: repeat and watch
X-Cache/CF-Cache-Statusflip toHIT, or aAgeheader appear. A cached, authenticated response is the vulnerability. - Prove cross-user impact: as the victim, visit the crafted URL once (or have them); then as an unauthenticated attacker request the same URL and receive the victim's private data.
- Explore delimiters/normalisation: caches and origins normalise
;,%2f,//,.., trailing dots differently — Param Miner's rules or manual fuzzing find the pair that splits them. - Report with least data: prove one private field leaked; don't hoard victim data.
Gotchas
- This is not cache poisoning: deception caches a victim's real response; poisoning injects a
malicious response via unkeyed input. Different bug, different report (
web-cache-poisoning). - Needs a genuinely cacheable-looking key and an origin that ignores it — confirm both.
- Some CDNs cache by content-type, not extension — test path-based tricks too.
Verify success
An unauthenticated request retrieves another user's authenticated content from the cache
(HIT/Age present), reproducibly.
References
Omer Gil "Web Cache Deception"; PortSwigger web cache deception labs; CDN caching-rule docs.
File di questa versione
- SKILL.md2.7 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | No | No |
| Usa la rete | No | No |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
La scansione non ha trovato nulla da segnalare in questa versione.
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | 56470805 | Firmata | – |
Altro da NoorQureshi
Tutto da questo editoreAltro in Web e bug bounty
Vai alla categoria- src-hunterzhaoxuya520/src-hunter5
- owasp-top10-analysissecurityskills/owasp-top10-analysis5
- testing-for-xml-injection-vulnerabilitiesmukul975/testing-for-xml-injection-vulnerabilities5
- offensive-xsssnailsploit/offensive-xss5
- offensive-rcesnailsploit/offensive-rce5
- source-review-techniqueaeondave/source-review-technique5
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login