Menu

1 / 5

“Web cache deception, explained: how a URL extension confuses the cache into storing your private page”

DEV Community: appsec·Martins Chibueze·10 days ago
#S1CuK5or
#devtoappsec#devto#dev#cache#response
Reading 0:00
15s threshold

Web cache deception (WCD) is when an attacker tricks the cache into storing a private, dynamic response by taking advantage of the differences in how the cache and the origin server each interpret a URL. The victim is lured into requesting an ambiguous URL; the cache mistakes their sensitive response for a cacheable static file and stores it; the attacker then requests the same URL and reads the victim’s cached data. It could either be by clicking a link or through phishing emails.

Web caches

A cache sits between client and origin server. On a cache miss it forwards the request to the origin, stores the response per its rules, then serves it; on a cache hit it serves the stored copy directly.

Cache key — the parts of the request (usually URL path + query string, sometimes headers/content type) used to decide if a stored response matches an incoming request.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.