Forum: Ruby on Rails [ANN] Rails 3.0.10

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
Aaron Patterson (Guest)
on 2011-08-17 01:34
(Received via mailing list)
Hi everyone,

Rails 3.0.10 has been released.  This release contains critical security


You can find an exhaustive list of changes on
[github](  Here
are some notable excerpts:

### 4 Security Fixes

  * [Filter Skipping
  * [SQL Injection
  * [Parse error in
  * [UTF-8 escaping

Please follow the links to see specific information about each
vulnerability, along with individual patches for fixing them.

Please note that these security fixes do not have CVE identifiers.  We
requested identifiers on August 5th, and have yet to received a
response.  When we get identifiers, we'll update the notices with those

Also remember to subscribe to the [Ruby on Rails Security mailing

### ActionPack:

  * Fixes an issue where cache sweepers with only after filters would
have no controller object, it would raise undefined method
`controller_name` for `nil` [jeroenj]
  * Ensure status codes are logged when exceptions are raised.
  * Subclasses of OutputBuffer are respected.
  * Fixed `ActionView::FormOptionsHelper#select` with `:multiple =>
  * Avoid extra call to `Cache#read` in case of a fragment cache hit

### ActiveRecord:

  * Magic encoding comment added to schema.rb files
  * schema.rb is written as UTF-8 by default.
  * Ensuring an established connection when running `rake
  * Association conditions will not clobber join conditions.
  * Destroying a record will destroy the HABTM record before destroying
itself.  GH #402.
  * Make `ActiveRecord::Batches#find_each` to not return `self`.
  * Update `table_exists?` in PG to to always use current `search_path`
or schema if explictly set.

### Why was this release delayed?

You may have noticed this release was originally slated to be released
on August 8th.  We decided to delay the release in order to obtain CVE
identifiers.  Unfortunately, identifiers still have not been issued.  We
felt that getting the security fixes to our users was more important
than obtaining CVE values.

That is why our release is late, and contains no CVE identifiers.


Thanks! <3
This topic is locked and can not be replied to.