Ruby on Rails Vulnerability Part III

Wednesday, January 30, 2013 @ 04:01 PM gHale


Another vulnerability exists with Ruby on Rails, this time with JavaScript Object Notation (JSON) code that could open the Web framework up to security problems.

Patches went out, but if left unpatched, the vulnerability could let attackers bypass authentication systems, inject arbitrary SQL code, inject and execute arbitrary code and perform a denial of service attack on a Ruby on Rails app.

RELATED STORIES
Ruby on Rails Bugs Patched, Part II
Ruby on Rails SQL Injection Hole
Ruby on Rails Patches Again
Trojan Hits Open Market

The vulnerability (CVE-2013-0333) affects older versions of the framework, versions 2.3.x and 3.0.x, according to an alert sent by software developer Michael Koziarski to the Ruby on Rails security group on Google Groups.

The vulnerability stems from a problem with the JSON parsing code that allows multiple parsing backends. For example, Ruby on Rails could parse YAML code, a markup format considered a superset of JSON. Since both forms of code are from the same family and both can end up parsed by Ruby on Rails, it’s possible an attacker could take a payload and “trick the backend into decoding a subset of YAML.”

The warning on Google Groups directs Ruby on Rails users to fix the flaw with two patches, “2-3-json-parser.patch” and “3-0-json-parser.patch.” If users are unable to apply the patches, they’re encouraged to create a workaround by switching their backend to the JSONGem backend.

Ruby on Rails has had other security woes of late. A SQL injection vulnerability affected all builds of the framework earlier this month that could’ve let an attacker inject code into web apps. While that quickly patched, another problem with the framework emerged a few days later. Bugs surfaced that could affect the way Ruby on Rails parses some parameters.

Similar to yesterday’s alert, a problem with the parser could have let attackers bypass authentication systems and inject arbitrary SQL, arbitrary code and open up the system to denial of service attacks. At the time, HD Moore, the creator of Metasploit warned the bug “is more than likely the worst security issue that the Rails platform has seen to date.” Exploit code and a Metasploit module that worked against versions 2.x and 3.x were developed and released soon after.



Leave a Reply

You must be logged in to post a comment.