performing-web-cache-deception-attack

Execute web cache deception attacks by exploiting path normalization discrepancies between CDN caching layers and origin servers to cache and retrieve sensitive authenticated content.

Jump to install

Repository: xalgord/xalgorix
Last source activity: June 6, 2026 at 16:41
Detected SKILL.md language: English
Stars: 813
Forks: 146

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/xalgord/xalgorix --skill performing-web-cache-deception-attack

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

exploiting-http-request-smuggling

Detecting and exploiting HTTP request smuggling vulnerabilities caused by Content-Length and Transfer-Encoding parsing discrepancies between front-end and back-end servers.

2026-07-20

exploiting-oauth-misconfiguration

Identifying and exploiting OAuth 2.0 and OpenID Connect misconfigurations including redirect URI manipulation, token leakage, and authorization code theft during security assessments.

2026-07-20

exploiting-subdomain-takeover-vulnerabilities

Identifying and exploiting dangling DNS records pointing to unclaimed cloud services, enabling subdomain takeover for phishing, cookie stealing, and authentication bypass during authorized penetration tests.

2026-06-19

View all from this repository

Performing Web Cache Deception Attack

When to Use

When testing applications behind CDNs or reverse proxies (Cloudflare, Akamai, Varnish, Nginx)

During assessment of authenticated page caching behavior

When evaluating path normalization differences between caching and origin layers

During bug bounty hunting on applications with aggressive caching policies

When testing for sensitive data exposure through cache layer misconfiguration

How to CONFIRM a Hit (avoid false negatives)

Positive signal: an authenticated response gets stored under a static-looking path and is then readable by a completely anonymous client — confirm with the second, unauthenticated request returning the victim's data and X-Cache: HIT / CF-Cache-Status: HIT / Age > 0.

The whole vulnerability lives in the second read: a single authenticated request that returns profile data proves nothing on its own.

Do NOT conclude "not vulnerable" until you have:

Performed the anonymous follow-up (no cookies/no auth header) to the exact crafted URL and confirmed it returns the victim's private content.
Confirmed the response was actually cached (HIT / positive Age), not just that the origin echoed the page.
Tried multiple static extensions (.css .js .png .jpg .svg .ico .woff2) and multiple delimiter/normalization tricks (;, %2f, %3b, %00, ..%2f, /., case changes) — caching rules vary by extension and by path-parsing discrepancy.
Tested several authenticated endpoints (profile, settings, billing) since caching rules are path-specific.
Ruled out per-user Vary: Cookie keying that would make the "hit" actually serve a non-victim copy.

Prerequisites

Understanding of HTTP caching mechanisms (Cache-Control, Vary, Age headers)

Knowledge of CDN path normalization and cache key construction

Burp Suite for intercepting and crafting requests

Two browser sessions (authenticated victim and unauthenticated attacker)

Understanding of URL path parsing differences across technologies

Familiarity with common CDN platforms (Cloudflare, Akamai, Fastly, AWS CloudFront)