<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>CSRF on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/tags/csrf/</link>
    <description>Recent content in CSRF on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 02 Aug 2013 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/tags/csrf/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Cross-Site Request Forgery with Cross-Origin Resource Sharing</title>
      <link>https://insinuator.net/2013/08/cross-site-request-forgery-with-cross-origin-resource-sharing/</link>
      <pubDate>Fri, 02 Aug 2013 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2013/08/cross-site-request-forgery-with-cross-origin-resource-sharing/</guid>
      <description>&lt;p&gt;During one of our last projects in a large environment we encountered an interesting flaw. Although it was not possible to exploit it in this particular context, it’s worth to be mentioned here. The finding was about &lt;a href=&#34;https://www.owasp.org/index.php/CSRF&#34; title=&#34;OWASP CSRF&#34;&gt;Cross-Site Request Forgery&lt;/a&gt;, a quite well-known attack that forces a user to execute unintended actions within the authenticated context of a web application. With a little help of social engineering (like sending a link via email, chat, embedded code in documents, etc…) an attacker may force the user to execute actions of the attacker’s choice.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
