<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Attacks on Sandeep Kumar</title><link>https://sandeep007734.github.io/tags/attacks/</link><description>Recent content in Attacks on Sandeep Kumar</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 12 Mar 2020 00:00:00 +0530</lastBuildDate><atom:link href="https://sandeep007734.github.io/tags/attacks/feed.xml" rel="self" type="application/rss+xml"/><item><title>Attacks on the control flow integrity of applications</title><link>https://sandeep007734.github.io/posts/attacks/bufferoverflow/</link><pubDate>Thu, 12 Mar 2020 00:00:00 +0530</pubDate><guid>https://sandeep007734.github.io/posts/attacks/bufferoverflow/</guid><description>&lt;h2 id="buffer-overflow-attacks"&gt;Buffer overflow attacks&lt;/h2&gt;
&lt;p&gt;Buffer overflow attack basically means that the content provided by the user to an application has a bigger size than what the application was expecting. In this case, if the application did not handle this kind of situation, then the user provided content will overwrite the stack of the application. In most cases this will corrupt the stack and the program will end with a segmentation fault.&lt;/p&gt;</description></item></channel></rss>