Web cache deception
A path/cache-policy discrepancy stores a private response for retrieval by another client.
Candidate CWE: CWE-524
Test hypothesis#
In an isolated local cache, place A’s private marker on a page. Compare its canonical route with one variant treated as static; request the variant as A and then anonymous B.
Evidence required#
B receives A’s marker because of cache behavior, while direct/fresh-key controls deny it. Save normalized routes, cache policy, and both client requests.
Rule out false positives#
A public share URL, application-level BOLA without caching, or the tester’s authenticated browser cache is not cache deception.
Playbook and command references#
- Proxy normalization, cache isolation, and request boundaries — Investigate layered HTTP behavior with isolated cache keys and controlled front-end/back-end traffic.
Find the associated command snippets
Referenced by these target playbooks#
Report checklist#
- Capture the affected version, configuration, identities, and object ownership.
- Preserve a valid baseline and a negative control.
- Reproduce the forbidden data access, action, or state change on controlled fixtures.
- Explain the intended security rule and why the observed behavior violates it.
- State prerequisites, uncertainty, cleanup, and the smallest demonstrated impact.
Conditional ATT&CK mapping#
No direct ATT&CK mapping selected. Record the weakness and demonstrated impact without forcing an adversary-behavior classification. See the mapping guide.