<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Web-Cache-Poisoning on </title>
    <link>https://anashamidi.com/tags/web-cache-poisoning/</link>
    <description>Recent content in Web-Cache-Poisoning on </description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 05 Apr 2024 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://anashamidi.com/tags/web-cache-poisoning/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Don&#39;t Trust the Cache: Exposing Web Cache Poisoning and Deception Vulnerabilities</title>
      <link>https://anashamidi.com/posts/web-cache-poisoning-and-deception/</link>
      <pubDate>Fri, 05 Apr 2024 00:00:00 +0000</pubDate>
      <guid>https://anashamidi.com/posts/web-cache-poisoning-and-deception/</guid>
      <description>&lt;p&gt;Good day! I hope you&amp;rsquo;re doing well.&lt;/p&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve been studying web cache vulnerabilities, so here&amp;rsquo;s a shortcut through all the different techniques I&amp;rsquo;ve come across so far. I&amp;rsquo;ll assume you already have a basic understanding of web caching concepts.&lt;/p&gt;&#xA;&lt;p&gt;الحمدلله والصلاة والسلام على رسول الله&lt;/p&gt;&#xA;&lt;p&gt;Obviously, the cache itself isn&amp;rsquo;t a vulnerability. What makes web applications vulnerable to web cache attacks is either chaining them with other bugs (most often XSS) or abusing misconfigurations to launch a Denial-of-Service (DoS) attack on the site.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
