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
Potential SQL Injection in Rails 3.0.x
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
 
Michael Koziarski  
View profile  
 More options Feb 8 2011, 3:53 pm
From: Michael Koziarski <mich...@koziarski.com>
Date: Wed, 09 Feb 2011 09:53:40 +1300
Local: Tues, Feb 8 2011 3:53 pm
Subject: Potential SQL Injection in Rails 3.0.x
Print | Individual message | Show original | Report this message | Find messages by this author

There is a vulnerability in the limit() function in Rails 3.0.x. This
vulnerability has been assigned the CVE identifier CVE-2011-0448.

Versions Affected:  3.0.0-3.0.3
Not affected:       Releases before 3.0.0
Fixed Versions:     3.0.4

Impact
------
All users running an affected release should either upgrade or use one
of the work arounds immediately.

Releases
--------
The 3.0.4 release is available at the normal location.

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

Users should convert any values provided to the limit() function into
integers explicitly.  For example code which is currently:

  @posts = Post.limit(params[:per_page]).all

Should become:

  @posts = Post.limit(params[:per_page].to_i).all

Patches
-------
Given the simplicity of the of workarounds and the low risk of the
upgrade, we will not be backporting this change to earlier releases.

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.

Credits
-------

Thanks to Eaden McKee from Webforce Ltd for reporting the bug to us.

--
Cheers,

Koz

  3-0-limit.patch
5K Download

  signature.asc
< 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