A city portal caches authenticated resident pages on a shared CDN edge. During a web assessment, what risk should the tester prioritize documenting?
Select an answer to reveal the explanation.
Short Explanation
Picture a shared locker room where someone hangs your badge on the public pegs by mistake. Caching private, logged-in pages on a shared CDN edge is like that — the next visitor may pull someone else's private page. The finding is about cache deception/poison class leakage, not about CDNs magically breaking TLS or SQL.
Full Explanation
Shared CDN caches that store authenticated or personalized responses can expose one user's content to subsequent requesters when cache keys, Vary headers, or Cache-Control directives are wrong. Testers should flag this as a confidentiality finding in the web cache misuse class. CDN presence does not eliminate origin injection paths, nor does a logo change browser caching rules. Remediation guidance centers on never caching authenticated responses at shared edges and validating cache key design.