web-cache-deception

Identify and analyze web cache deception and poisoning vectors in CDN and reverse proxy deployments.

1.6k|204|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/yaklang/hack-skills --skill web-cache-deception
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-cache-deception
Source: https://github.com/yaklang/hack-skills/tree/main/skills/web-cache-deception
Command: npx skills add https://github.com/yaklang/hack-skills --skill web-cache-deception

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web cache deception and poisoning threaten to leak authenticated data or serve malicious content through CDN edges. This playbook helps security professionals identify, reason about, and defend against these caching vulnerabilities in real-world deployments.

Core Features & Use Cases

  • Clear distinction between web cache deception and cache poisoning, with attack-flow mappings.
  • Coverage of unkeyed inputs (headers like X-Forwarded-Host, X-Original-URL), unkeyed parameters, fat GETs, Vary header manipulation, and CDN-specific behaviors.
  • Practical testing, defense recommendations, and remediation steps for dynamic sites and APIs.

Quick Start

Load this playbook and begin applying the techniques to assess and remediate a target cache deployment.

Frequently Asked Questions about web-cache-deception

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the difference between web cache deception and web cache poisoning?

Web cache deception tricks a CDN into caching authenticated user data via path confusion, while cache poisoning injects malicious content into edge caches through unkeyed headers or parameters to serve harmful responses to users.

How do I test for unkeyed headers and Vary header manipulation in CDN caching?

Test CDN caching vulnerabilities by manipulating unkeyed headers like X-Forwarded-Host and X-Original-URL, analyzing fat GETs, and altering Vary headers to identify cache poisoning vectors that serve malicious content to users.

How does path confusion expose authenticated user data through reverse proxy caching?

Path confusion exploits reverse proxy caching rules by appending static extensions to dynamic URLs, tricking the cache into storing authenticated responses and exposing sensitive user data to unauthenticated visitors.

Can I apply web cache deception testing techniques to dynamic APIs and load balancers?

Yes, web cache deception and poisoning testing applies to CDNs, load balancers, and edge caches across dynamic websites and APIs, targeting unkeyed parameters, fat GETs, and CDN-specific behaviors to expose cache vulnerabilities.

What are the defense strategies against web cache poisoning and deception attacks?

Defend against web cache attacks by configuring proper Vary headers, securing unkeyed inputs, enforcing strict caching rules for authenticated content, and applying recommended testing procedures and remediation steps for dynamic sites and APIs.