Create a gist now

Instantly share code, notes, and snippets.

What would you like to do?

CVE-2013-3221 Outline / Work Arounds / Fixes / Credits

original link

Common patterns used in Ruby on Rails applications could allow an attacker to generate SQL that, when combined with some database server's typecasting code, generates queries that match incorrect records.

Note: This is a code and best-practise advisory, there is no patch to apply or updated version to install.

Databases Affected: MySQL, SQLServer and some configurations of DB2 Not affected: SQLite, PostgreSQL, Oracle


When comparing two values of differing types most databases will either generate an error or return 'false'. Other databases will attempt to convert those values to a common type to enable comparison.

For example in MySQL comparing a string with an integer will cast the string into an integer. Given that any string which isn't an invalid integer will convert to 0, this could allow an attacker to bypass certain queries.

If your application has XML or JSON parameter parsing enabled, an attacker will be able to generate queries like this unless you take care to typecast your input values. For example:


Could be made to generate the query:

SELECT * FROM `users` WHERE `login_token` = 0 LIMIT 1;

Which will match the first value which doesn't contain a valid integer. This vulnerability affects multiple programming languages, and multiple databases, be sure to audit your other applications to see if they suffer the same issues.

Work Arounds

There are two options to avoid these problems. The first is to disable JSON and XML parameter parsing. Depending on the version of rails you use you will have to place one of the following snippets in an application initializer

Rails 3.2, 3.1 and 3.0:


Rails 2.3:


If your application relies on accepting these formats you will have to take care to explicitly convert parameters to their intended types. For example:



Unfortunately it is not possible for ActiveRecord to automatically protect against all instances of this attack due to the API we expose. For example:

User.where("login_token = ? AND expires_at > ?", params[:token],

Without parsing the SQL fragments it is not possible to determine what type params[:token] should be cast to.

Future releases of Rails will contain changes to mitigate the risk of this class of vulnerability, however as long as this feature is still supported this risk will remain.


  • Thanks to joernchen of Phenoelit for reporting this to us and to
  • Jonathan Rudenberg for helping to review the advisory.
  • by Michael Koziarski
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment