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 instalaciones+5 en 7 días27 EstrellasMITsincronizado hace 22 horas
Instalar
¿Aún no tienes la CLI de NotHoly? Instálala primero.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/web-cache-deceptionEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paquete56470805…9adc140b
564708054e06…8f2b9adc140b1 archivo · 1.4 KBEscaneoBajosin hallazgos
Fuentegithub.com/NoorQureshi/security-skills/tree/main/skills/web/web-cache-deception@ee0e0c5
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
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.
Archivos de esta versión
- SKILL.md2.7 KB
Permisos
| Permiso | Declarado | Hallado en el escaneo |
|---|---|---|
| Lee archivos | No | No |
| Escribe archivos | No | No |
| Ejecuta comandos de shell | No | No |
| Usa la red | No | No |
| Usa conectores | No | No |
| Controla un navegador | No | No |
Hallazgos del escaneo
Revisado el 13 nov 2026
El escaneo no encontró nada que señalar en esta versión.
Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.
| Versión | Publicada | Commit | SHA-256 | Firma | Cambio de permisos |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | 56470805 | Firmada | – |
Más de NoorQureshi
Todo de este publicadorMás en Web y bug bounty
Ver la categoría- 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
Pregunta todo lo que tu alcance permite.
Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.
- 1/3
Crea la cuenta
Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.
IndividualEmpresa - 2/3
Añade créditos
Con tarjeta. Pagas por token, sin suscripción.
$5.00recarga mínima - 3/3
Pregunta
En el chat, o instala el CLI y ejecuta notholy login en tu terminal.
$ notholy login