Unsafe Query Generation Risk in Ruby on Rails (CVE-2013-0155)

Re:Unsafe Query Generation Risk in Ruby on Rails (CVE-2013-0... by teyc on Tuesday January 08, 2013 @09:52PM (#5029857)

Please, if anyone's reading this, do not release a proof-of-concept until everyone has a chance to patch. (I sense there are a lot of already busy Rails developers today).

By the way, what do freelancers on HN feel about general responsibility for security maintenance after the work has been done?

[ Parent | on HN ]

Re:Unsafe Query Generation Risk in Ruby on Rails (CVE-2013-0... by j-kidd on Tuesday January 08, 2013 @11:59PM (#5030245)

I have never done any Ruby / Rails development, but this exploit doesn't look like it requires any proof-of-concept.

My understanding is that as long as there is a JSON endpoint accepting parameters, and the parameters are used for query generation without going through a proper validation layer [1], then the app is vulnerable.

[1] In python, this would be things like FormEncode, WTForms, Colander, etc.

[ Parent | on HN ]