<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/stylesheets/rss.css" type="text/css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Yup Dot Com: Beware of "Assumed Logged In" Attacks</title>
    <link>http://www.yup.com/articles/2006/08/30/beware-of-assumed-logged-in-attacks</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>Advanced Web Services</description>
    <item>
      <title>Beware of &amp;quot;Assumed Logged In&amp;quot; Attacks</title>
      <description>&lt;p&gt;&lt;img style="float: right; border: 1px dotted #ccc; margin: 4px; padding: 4px" src="http://static.flickr.com/54/128390795_3d16a30ee3_m.jpg" /&gt;
Brian Ellin of Portland, Oregon, warns us of &amp;#8220;assumed logged in&amp;#8221; attacks, which are cross-site attacks in which another site carefully crafts a URL that opens in a hidden frame which performs a destructive action on a different site that you are assumed to have been logged in to. His solution: the secure-action-plugin. He describes the problem and the solution:&lt;/p&gt;

&lt;blockquote&gt;

&lt;p&gt;In an assumed logged in attack, a malicious site assumes the visitor is logged into your site. The malicious site manually crafts a URL to a destructive action on your site (change email, delete account, etc.) and opens the URL to that action in a hidden iframe. The browser then sends the user’s cookies and actions may be performed on your user’s behalf without them ever knowing. This technique may be used to steal accounts, inject or delete account data, or perform other malicious actions.&lt;/p&gt;

&lt;p&gt;The plugin works by overriding ActionController.url_for and adding a signature of the user’s session_id and some salt to URL query strings. By adding a sig that includes the user’s session_id, it makes it impossible to for malicious sites to create URLs that will work on your site for anyone but themselves. The signature is verified before a secure action is executed.&lt;/p&gt;

&lt;/blockquote&gt;

&lt;p&gt;Until now, I had not conceived of this type of attack. Thanks, Brian. &lt;/p&gt;

&lt;p&gt;&lt;a href="http://wiki.rubyonrails.com/rails/pages/Secure+Action"&gt;Secure Action on the Rails Wiki Page&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://code.google.com/p/secure-action-plugin/"&gt;Plugin Home Page&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://www.agilewebdevelopment.com/plugins/secure_action_plugin"&gt;Ruby Plugins Directory Entry&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Wed, 30 Aug 2006 07:01:00 -0400</pubDate>
      <guid isPermaLink="false">urn:uuid:a982cd27-e9e4-43fc-aab0-ba103c08600c</guid>
      <author>Daniel Butler</author>
      <link>http://www.yup.com/articles/2006/08/30/beware-of-assumed-logged-in-attacks</link>
      <category>Ruby on Rails</category>
    </item>
  </channel>
</rss>
