CVE-2012-6496

Publication date 4 January 2013

Last updated 24 July 2024


Ubuntu priority

SQL injection vulnerability in the Active Record component in Ruby on Rails before 3.0.18, 3.1.x before 3.1.9, and 3.2.x before 3.2.10 allows remote attackers to execute arbitrary SQL commands via a crafted request that leverages incorrect behavior of dynamic finders in applications that can use unexpected data types in certain find_by_ method calls.

Read the notes from the security team

Status

Package Ubuntu Release Status
rails 17.04 zesty
Not affected
16.10 yakkety
Not affected
16.04 LTS xenial
Not affected
15.10 wily
Not affected
15.04 vivid
Not affected
14.10 utopic
Not affected
14.04 LTS trusty Not in release
13.10 saucy
Not affected
13.04 raring
Not affected
12.10 quantal
Not affected
12.04 LTS precise
Not affected
11.10 oneiric
Not affected
10.04 LTS lucid Ignored end of life
8.04 LTS hardy Ignored end of life
ruby-activerecord-2.3 17.04 zesty Not in release
16.10 yakkety Not in release
16.04 LTS xenial Not in release
15.10 wily Not in release
15.04 vivid Not in release
14.10 utopic Not in release
14.04 LTS trusty Not in release
13.10 saucy Ignored end of life
13.04 raring Ignored end of life
12.10 quantal Ignored end of life
12.04 LTS precise Ignored end of life
11.10 oneiric Ignored end of life
10.04 LTS lucid Not in release
8.04 LTS hardy Not in release
ruby-activerecord-3.2 17.04 zesty Not in release
16.10 yakkety Not in release
16.04 LTS xenial Not in release
15.10 wily Not in release
15.04 vivid Not in release
14.10 utopic Not in release
14.04 LTS trusty Not in release
13.10 saucy
Not affected
13.04 raring Ignored end of life
12.10 quantal Ignored end of life
12.04 LTS precise Not in release
11.10 oneiric Not in release
10.04 LTS lucid Not in release
8.04 LTS hardy Not in release

Notes


mdeslaur

in Oneiric+, rails package is just for transition


seth-arnold

The authlogic gem was frequently cited as the problem in early reports, but the problem is with core Active Record. authlogic was just one vector known to allow exploiting the problem. CVE-2012-5664 was rejected as a result of the confusion.