Ruby on Rails 3.0.x before 3.0.4 does not ensure that arguments to the limit function specify integer values, which makes it easier for remote attackers to conduct SQL injection attacks via a non-numeric argument.
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
| Link | Tags |
|---|---|
| http://groups.google.com/group/rubyonrails-security/msg/4e19864cf6ad40ad?dmode=source&output=gplain | mailing list patch |
| http://weblog.rubyonrails.org/2011/2/8/new-releases-2-3-11-and-3-0-4 | patch |
| http://securitytracker.com/id?1025063 | vdb entry |
| http://lists.fedoraproject.org/pipermail/package-announce/2011-April/057650.html | vendor advisory |
| http://secunia.com/advisories/43278 | third party advisory vendor advisory |
| http://www.vupen.com/english/advisories/2011/0877 | vdb entry |
| https://github.com/rails/rails/commit/354da43ab0a10b3b7b3f9cb0619aa562c3be8474 |