https://wiki.owasp.org/api.php?action=feedcontributions&feedformat=atom&user=PshanksOWASP - User contributions [en]2026-04-04T01:56:08ZUser contributionsMediaWiki 1.27.2https://wiki.owasp.org/index.php?title=Cache_Poisoning&diff=13172Cache Poisoning2006-11-17T06:52:32Z<p>Pshanks: /* Description */</p>
<hr />
<div>{{Template:Attack}}<br />
{{Template:Fortify}}<br />
<br />
==Description==<br />
<br />
The impact of a maliciously constructed response can be magnified if it is cached either by a web cache used by multiple users or even the browser cache of a single user. If a response is cached in a shared web cache, such as those commonly found in proxy servers, then all users of that cache will continue receive the malicious content until the cache entry is purged. Similarly, if the response is cached in the browser of an individual user, then that user will continue to receive the malicious content until the cache entry is purged, although only the user of the local browser instance will be affected.<br />
<br />
==Examples ==<br />
<br />
==Related Threats==<br />
<br />
==Related Attacks==<br />
<br />
[[HTTP Response Splitting]]<br />
<br />
==Related Vulnerabilities==<br />
<br />
[[:Category:Input Validation Vulnerability]]<br />
<br />
==Related Countermeasures==<br />
<br />
[[:Category:Input Validation]]<br />
<br />
==Categories==</div>Pshanks