cache-poisoning

To detect web cache poisoning vulnerabilities, analyze the CDN-backed application's caching behavior to identify unkeyed headers and parameters that allow crafted requests to persist poisoned cached responses affecting other users.

Test unkeyed headers for cache poisoning by evaluating parameter normalization issues and reflected content. This process identifies whether crafted headers create persistent cached responses that trigger XSS risks or cache denial-of-service scenarios for other users.

Yes, this cache poisoning detection applies to reverse proxy security assessments. It evaluates unsafe cache behavior and unkeyed request components across CDN, reverse proxy, and application caching layers to validate vulnerabilities.

A cache key determines unique cached responses based on specific request components. Vulnerability testing analyzes cache keys to find unkeyed inputs that enable web cache poisoning, allowing attackers to manipulate responses served to other users.

Yes, you can validate cache poisoning safely using safe proof-of-concept testing capabilities. This approach verifies unsafe cache behavior and reflected content risks through controlled cache fingerprinting and cache key analysis without impacting production traffic.