<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <id>http://groups.google.com/group/rubyonrails-security</id>
  <title type="text">Ruby on Rails: Security Google Group</title>
  <subtitle type="text">
  Security annoucements for Ruby on Rails.
  </subtitle>
  <link href="/group/rubyonrails-security/feed/atom_v1_0_msgs.xml" rel="self" title="Ruby on Rails: Security feed"/>
  <updated>2008-08-23T15:41:37Z</updated>
  <generator uri="http://groups.google.com" version="1.99">Google Groups</generator>
  <entry>
  <author>
  <name>Michael Koziarski</name>
  <email>mich...@koziarski.com</email>
  </author>
  <updated>2008-08-23T15:41:37Z</updated>
  <id>http://groups.google.com/group/rubyonrails-security/browse_thread/thread/9fb60a1e22a88d30/330bcb96de877996?show_docid=330bcb96de877996</id>
  <link href="http://groups.google.com/group/rubyonrails-security/browse_thread/thread/9fb60a1e22a88d30/330bcb96de877996?show_docid=330bcb96de877996"/>
  <title type="text">Re: DoS Vulnerabilities in REXML</title>
  <summary type="html" xml:space="preserve">
  The rexml-expansion-fix gem is now available from rubyforge and its &lt;br&gt; mirrors. To install it you need to run: &lt;br&gt; gem install rexml-expansion-fix &lt;br&gt; Once that command has completed add the following line to the bottom &lt;br&gt; of your environment.rb file: &lt;br&gt; require &#39;rexml-expansion-fix&#39; &lt;br&gt; With that, your application will no longer be vulnerable.
  </summary>
  </entry>
  <entry>
  <author>
  <name>Michael Koziarski</name>
  <email>mich...@koziarski.com</email>
  </author>
  <updated>2008-08-23T08:10:19Z</updated>
  <id>http://groups.google.com/group/rubyonrails-security/browse_thread/thread/9fb60a1e22a88d30/64d4873c273c8e97?show_docid=64d4873c273c8e97</id>
  <link href="http://groups.google.com/group/rubyonrails-security/browse_thread/thread/9fb60a1e22a88d30/64d4873c273c8e97?show_docid=64d4873c273c8e97"/>
  <title type="text">DoS Vulnerabilities in REXML</title>
  <summary type="html" xml:space="preserve">
  The ruby-security team have published an advisory[1] about a DoS bug &lt;br&gt; affecting REXML users. Most rails applications will be affected by &lt;br&gt; this vulnerability and you&#39;re strongly advised to take the mitigating &lt;br&gt; steps recommended in the advisory. &lt;br&gt; The announcement contains details describing a monkeypatch which can
  </summary>
  </entry>
  <entry>
  <author>
  <name>Michael Koziarski</name>
  <email>mich...@koziarski.com</email>
  </author>
  <updated>2007-11-24T22:16:29Z</updated>
  <id>http://groups.google.com/group/rubyonrails-security/browse_thread/thread/1bea46abaebb2998/82eb2bccfafe4948?show_docid=82eb2bccfafe4948</id>
  <link href="http://groups.google.com/group/rubyonrails-security/browse_thread/thread/1bea46abaebb2998/82eb2bccfafe4948?show_docid=82eb2bccfafe4948"/>
  <title type="text">Ruby on Rails 1.2.6</title>
  <summary type="html" xml:space="preserve">
  The rails core team has released ruby on rails 1.2.6 to address a bug &lt;br&gt; in the fix for session fixation attacks(CVE-2007-5380). The CVE &lt;br&gt; Identifier for this new issue is CVE-2007-6077. &lt;br&gt; You should upgrade to this new release if you do not take specific &lt;br&gt; session-fixation counter measures in your application. 1.2.6 also
  </summary>
  </entry>
  <entry>
  <author>
  <name>Michael Koziarski</name>
  <email>mich...@koziarski.com</email>
  </author>
  <updated>2007-10-12T22:30:23Z</updated>
  <id>http://groups.google.com/group/rubyonrails-security/browse_thread/thread/034c7766ca4d5505/73a2f473a483b866?show_docid=73a2f473a483b866</id>
  <link href="http://groups.google.com/group/rubyonrails-security/browse_thread/thread/034c7766ca4d5505/73a2f473a483b866?show_docid=73a2f473a483b866"/>
  <title type="text">Ruby on Rails 1.2.5</title>
  <summary type="html" xml:space="preserve">
  The rails core team has released ruby on rails 1.2.5 to address a &lt;br&gt; potential XSS exploit with our json serialization. The CVE Identifier &lt;br&gt; for this problem is CVE-2007-3227. &lt;br&gt; You are only at risk if you embed the result of a .to_json call in a &lt;br&gt; page you generate. For example: &lt;br&gt; &amp;lt;script type=&amp;quot;text/javascript&amp;quot;&amp;gt;
  </summary>
  </entry>
  <entry>
  <author>
  <name>Michael Koziarski</name>
  <email>mich...@koziarski.com</email>
  </author>
  <updated>2007-10-12T22:25:00Z</updated>
  <id>http://groups.google.com/group/rubyonrails-security/browse_thread/thread/239b034f4f808834/e3473b373afff5a0?show_docid=e3473b373afff5a0</id>
  <link href="http://groups.google.com/group/rubyonrails-security/browse_thread/thread/239b034f4f808834/e3473b373afff5a0?show_docid=e3473b373afff5a0"/>
  <title type="text">Re: Ruby on Rails 1.2.4</title>
  <summary type="html" xml:space="preserve">
  The issues mentioned in this advisory now have CVE numbers. &lt;br&gt; CVE-2007-5379 &lt;br&gt; CVE-2007-5380 &lt;br&gt; This was a typo, to re-enable URL based sessions you need the &lt;br&gt; following line in your environment.rb file. &lt;br&gt; config.action_controller.sessi on_options[:cookie_only] = false
  </summary>
  </entry>
  <entry>
  <author>
  <name>DHH</name>
  <email>david.heineme...@gmail.com</email>
  </author>
  <updated>2007-10-12T16:50:53Z</updated>
  <id>http://groups.google.com/group/rubyonrails-security/browse_thread/thread/225dcc61aaefad42/4b6c62c789ad64f2?show_docid=4b6c62c789ad64f2</id>
  <link href="http://groups.google.com/group/rubyonrails-security/browse_thread/thread/225dcc61aaefad42/4b6c62c789ad64f2?show_docid=4b6c62c789ad64f2"/>
  <title type="text">Rails 1.2.5: Closes JSON XSS vulnerability</title>
  <summary type="html" xml:space="preserve">
  This release closes a JSON XSS vulnerability, fixes a couple of minor &lt;br&gt; regressions introduced in 1.2.4, and backports a handful of features &lt;br&gt; and fixes from the 2.0 preview release. &lt;br&gt; All users of Rails 1.2.4 or earlier are advised to upgrade to 1.2.5, &lt;br&gt; though it isn&#39;t strictly necessary if you aren&#39;t working with JSON.
  </summary>
  </entry>
  <entry>
  <author>
  <name>Michael Koziarski</name>
  <email>mich...@koziarski.com</email>
  </author>
  <updated>2007-10-10T01:33:45Z</updated>
  <id>http://groups.google.com/group/rubyonrails-security/browse_thread/thread/239b034f4f808834/439c36b0eee81b47?show_docid=439c36b0eee81b47</id>
  <link href="http://groups.google.com/group/rubyonrails-security/browse_thread/thread/239b034f4f808834/439c36b0eee81b47?show_docid=439c36b0eee81b47"/>
  <title type="text">Ruby on Rails 1.2.4</title>
  <summary type="html" xml:space="preserve">
  The release of Ruby on Rails 1.2.4 addresses some potential security &lt;br&gt; issues, all users of earlier versions are advised to upgrade to 1.2.4: &lt;br&gt; The particular issues are: &lt;br&gt; Maliciously crafted requests to a rails application could cause the &lt;br&gt; XML parser to read files from the server&#39;s disk or the network. 1.2.4
  </summary>
  </entry>
</feed>
