<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Xss on Shivasurya</title><link>http://shivasurya.me/tags/xss/</link><description>Recent content in Xss on Shivasurya</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 07 Dec 2020 00:00:00 +0000</lastBuildDate><atom:link href="http://shivasurya.me/tags/xss/feed.xml" rel="self" type="application/rss+xml"/><item><title>Cross-Site Scripting attack on Leetcode</title><link>http://shivasurya.me/2020/12/07/leetcode-xss/</link><pubDate>Mon, 07 Dec 2020 00:00:00 +0000</pubDate><guid>http://shivasurya.me/2020/12/07/leetcode-xss/</guid><description>&lt;p>Reflected XSS (Cross-Site Scripting) attack is my favorite vulnerability category as it&amp;rsquo;s relatively easy to exploit by checking for params as the source and rendering DOM as the sink.&lt;/p>
&lt;h3 id="problem">Problem&lt;/h3>
&lt;p>The core problem of the Reflected Cross-Site scripting attack is appending the URL parameter values in the DOM without validation or filtering. Though the reflected XSS requires user interaction by visiting the page or clicking on links in real-life attacks, people should think about Iframe tags that don&amp;rsquo;t need any interaction to load them on other third party web pages.&lt;/p></description></item></channel></rss>