<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacks on System Overlord</title><link>https://systemoverlord.com/tags/hacks.html</link><description>Recent content in Hacks on System Overlord</description><generator>Hugo</generator><language>en-us</language><managingEditor>david@systemoverlord.com (David Tomaschik)</managingEditor><webMaster>david@systemoverlord.com (David Tomaschik)</webMaster><lastBuildDate>Wed, 24 Aug 2016 00:00:00 +0000</lastBuildDate><atom:link href="https://systemoverlord.com/tags/hacks/index.xml" rel="self" type="application/rss+xml"/><item><title>Posting JSON with an HTML Form</title><link>https://systemoverlord.com/2016/08/24/posting-json-with-an-html-form.html</link><pubDate>Wed, 24 Aug 2016 00:00:00 +0000</pubDate><author>david@systemoverlord.com (David Tomaschik)</author><guid>https://systemoverlord.com/2016/08/24/posting-json-with-an-html-form.html</guid><description>&lt;p&gt;A coworker and I were looking at an application today that, like so many other
modern web applications, offers a RESTful API with JSON being used for
serialization of requests/responses. She noted that the application didn&amp;rsquo;t
include any sort of CSRF token and didn&amp;rsquo;t seem to use any of the headers
(X-Requested-With, Referer, Origin, etc.) as a &amp;ldquo;poor man&amp;rsquo;s CSRF token&amp;rdquo;, but
since it was posting JSON, was it really vulnerable to CSRF? &lt;strong&gt;Yes, yes,
definitely yes!&lt;/strong&gt;&lt;/p&gt;</description></item></channel></rss>