Featured Articles

Intel releases tiny 3G cell modem

Intel releases tiny 3G cell modem

Intel has released a 3G cellular modem with an integrated power amplifier that fits into a 300 mm2 footprint, claiming it…

More...
Braswell 14nm Atom slips to Q2 15

Braswell 14nm Atom slips to Q2 15

It's not all rosy in the house of Intel. It seems that upcoming Atom out-of-order cores might be giving this semiconductor…

More...
TSMC 16nm wafers coming in Q1 2015

TSMC 16nm wafers coming in Q1 2015

TSMC will start producing 16nm wafers in the first quarter of 2015. Sometime in the second quarter production should ramp up…

More...
Skylake-S LGA is 35W to 95W TDP part

Skylake-S LGA is 35W to 95W TDP part

Skylake-S is the ‘tock’ of the Haswell architecture and despite being delayed from the original plan, this desktop part is scheduled…

More...
Aerocool Dead Silence reviewed

Aerocool Dead Silence reviewed

Aerocool is well known for its gamer cases with aggressive styling. However, the Dead Silence chassis offers consumers a new choice,…

More...
Frontpage Slideshow | Copyright © 2006-2010 orks, a business unit of Nuevvo Webware Ltd.
Friday, 04 January 2013 10:48

Ruby on Rails vulnerable

Written by Nick Farrell



SQL injection vulnerability

All of the current versions of the Ruby on Rails Web framework are shipping with a SQL injection vulnerability which means that hackers can inject code into Web applications. 

The maintainers of Ruby on Rails have released new versions that fixes the flaw, versions 3.2.10, 3.1.9 and 3.0.18 but given that it is a popular framework for developing Web apps things could get messy. The open-source framework is used by a wide variety of organisations and the flaw is in the way that dynamic finders in Active Record extract options from method parameters.

The dynamic finders in Active Record extract options from method parameters, a method parameter can mistakenly be used as a scope. This means that a dodgy request can use the scope to inject arbitrary SQL, the advisory says. All users running an affected release should either upgrade or use one of the work arounds immediately.

The advisory recommends that users running affected versions, which is essentially anyone using Ruby on Rails, upgrade immediately to one of the fixed versions, 3.2.10, 3.1.9 or 3.0.18. The vulnerability doesn't mean that all of the apps developed on vulnerable versions are susceptible to the bug.

Nick Farrell

E-mail: This e-mail address is being protected from spambots. You need JavaScript enabled to view it
blog comments powered by Disqus

 

Facebook activity

Latest Commented Articles

Recent Comments