Cache Poisoning

To detect web cache poisoning in Nginx and CDNs, search your proxy configurations for vulnerable `proxy_cache_key` directives and verify if dynamic content is improperly cached under static file extensions. This identifies misconfigurations across application, proxy, and CDN layers.

Web cache poisoning manipulates cache keys via headers to serve malicious content to users, while web cache deception tricks caches into storing sensitive dynamic content under static file extensions. This Skill analyzes both vulnerabilities across proxy and CDN layers to prevent unauthorized data exposure.

Prevent SSRF-to-cache poisoning by analyzing your application for path extension abuse and cache key manipulation via headers. This Skill identifies SSRF-to-cache poisoning chains and provides specific remediation steps and secure caching practices for your Nginx, proxy, and CDN configurations.

Yes, this Skill analyzes cache misconfigurations across Varnish and Cloudflare environments. It identifies cache key manipulation via headers and provides specific configuration examples to secure caching practices across your application, proxy, and CDN layers.

Your Nginx proxy cache likely serves incorrect content due to a vulnerable `proxy_cache_key` directive causing cache poisoning. This Skill helps search your codebase for misconfigurations and checks if dynamic content is being cached under static file extensions.

The best way to remediate HTTP cache poisoning is by applying secure caching configurations. This Skill provides specific remediation examples for Nginx, application code, and CDN settings to fix cache key manipulation and path extension abuse vulnerabilities.