WCD - WCP

Web Cache Poisoning/Deception

Web Cache Deception

Web Cache Deception

To test for web cache deception try one of the several path confusing payloads as shown below: ● example.com/nonexistent.css ● example.com/%0nonexistent.css ● example.com/%3Bnonexistent.css ● example.com/%23nonexistent.css ● example.com/%3Fname=valnonexistent.css

β€’ Use less known extensions such as .avif

chat.openai[.]com/api/auth/session.css β†’ 400

chat.openai[.]com/api/auth/session/test.css β†’ 200

Omer Gil: Web Cache Deception Attack

Cache Poisoning and Cache Deception

The difference

What is the difference between web cache poisoning and web 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.

References

Top Web Cache reports from HackerOne:

  1. DoS on PayPal via web cache poisoning to PayPal - 811 upvotes, $9700

  2. Web Cache Poisoning leads to Stored XSS to Glassdoor - 99 upvotes, $0

  3. Web Cache Poisoning leads to XSS and DoS to Glassdoor - 55 upvotes, $0

  4. Web Cache Deception Attack (XSS) to Discourse - 33 upvotes, $256

  5. Web Cache Poisoning on β–ˆβ–ˆβ–ˆβ–ˆβ–ˆ to U.S. Dept Of Defense - 32 upvotes, $0

  6. Web Cache Deception Attack (XSS) to Algolia - 21 upvotes, $0

  7. Web Cache Poisoning to Mail.ru - 17 upvotes, $0

  8. Web cache poisoning at www.acronis.com to Acronis - 15 upvotes, $0

  9. Web Cache Poisoning leading to DoS to U.S. General Services Administration - 13 upvotes, $0

Last updated