Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Ruby on Rails: Security
Home
About this group
Join this group
SQL Injection Vulnerability in quote_table_name
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Aaron Patterson  
View profile  
 More options Aug 16 2011, 5:02 pm
From: Aaron Patterson <aa...@tenderlovemaking.com>
Date: Tue, 16 Aug 2011 14:02:30 -0700
Local: Tues, Aug 16 2011 5:02 pm
Subject: SQL Injection Vulnerability in quote_table_name
Print | Individual message | Show original | Report this message | Find messages by this author

SQL Injection Vulnerability in quote_table_name

There is a vulnerability in the quote_table_name method which could allow malicious users to inject arbitrary SQL into a query. This vulnerability has been assigned the CVE identifier CVE-YYYY-XXXX.

Versions Affected:  All.
Fixed Versions:     3.0.10, 2.3.13, 3.1.0.rc5

Impact
------

The quote_table_name method in the ActiveRecord adapaters for Ruby on Rails were initially created solely for the purpose of escaping reserved words encountered in table names.  However over time 3rd party libraries, and rails itself, grew to rely on those functions as a way to sanitize potentially malicious user input.  As a result these functions need to be hardened to manage malicious input rather than assuming they're being passed benign values generated by rails itself.

All users running an affected release should upgrade immediately.

Releases
--------

The 3.0.10, 2.3.13 and v3.1.0.rc5 releases are available at the normal locations.

Workarounds
-----------

There are no feasible workarounds for this issue.

Patches
-------
To aid users who aren't able to upgrade immediately we have provided patches for the two supported release series.  They are in git-am format and consist of a single changeset.

* 2-3-sql_injection.patch - Patch for 2.3 series
* 3-0-sql_injection.patch - Patch for 3.0 series
* 3-1-sql_injection.patch - Patch for 3.1 series

Please note that only the  2.3.x and 3.0.x series are supported at present.  Users of earlier unsupported releases are advised to upgrade as soon as possible.

--
Aaron Patterson
http://tenderlovemaking.com/

  2-3-stable-fix-sql-injection.patch
2K Download

  3-0-stable-fix-sql-injection.patch
2K Download

  3-1-stable-fix-sql-injection.patch
3K Download

  application_pgp-signature_part
< 1K Download

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google