News for hackers. Stuff that matters.
Re:What The Rails Security Issue Means For Your Startup by hawleyal on Thursday January 31, 2013 @01:43PM (#5146539)
ಠ_ಠ

Because other frameworks are rock-solid. Yup. None of this happens anywhere else on the internet.

Re:What The Rails Security Issue Means For Your Startup by raganwald on Thursday January 31, 2013 @03:59PM (#5147430)
Doesn't matter whether this happens elsewhere. It's still bad. Here's a near-Godwin-like example. If I say that gun violence is a problem in the USA, you could say "Hey! You're up in Canada, what happened with that guy who gunned down 14 women in Québec? Gun violence happens everywhere!"

It does happen everywhere. It should be stopped everywhere. But it happens more frequently in some places. There are special conditions that permit it to happen in some places.And if it is a serious concern of yours, knowing where it is and isn't most likely likely to happen again is important.

Re:What The Rails Security Issue Means For Your Startup by mpyne on Thursday January 31, 2013 @04:30PM (#5147608)
Well, both the Python and Perl guys at least seem to have a healthier awareness of how dangerous untrusted arbitrary data can be (e.g. http://docs.python.org/2/library/pickle.html)

The Perl YAML warning is less obvious but they at least mention in their LoadCode docs (http://search.cpan.org/~mstrout/YAML-0.84/lib/YAML.pm) that you have to specifically enable code deserialization since untrusted evaluation is a bad idea.

Python's YAML is only slightly worse, with an available safe_load method that refuses to run code (and a failure to use appropriately led to vulns in popular Django plugins a little more than a year ago).

There's no easy equivalent to safe_load or UseCode for Ruby's YAML (http://apidock.com/ruby/Psych) as far as I can tell, at least while still using the high-level parser. And I'll note that the API docs I provided are for the new YAML parser introduced with 1.9.3. I would like to think that by 2010 there would be a general awareness of the risk of using deserializers/code emitters on untrusted input.

Re:What The Rails Security Issue Means For Your Startup by lucian1900 on Thursday January 31, 2013 @03:40PM (#5147307)
Nothing quite this catastrophic tends to happen to things that aren't PHP.
Re:What The Rails Security Issue Means For Your Startup by steveklabnik on Thursday January 31, 2013 @04:06PM (#5147464)
That is simply not true. Here's an example linked upthread for Struts, for example: http://blog.o0o.nu/2010/07/cve-2010-1870-struts2xwork-remote...
Re:What The Rails Security Issue Means For Your Startup by static_typed on Thursday January 31, 2013 @04:57PM (#5147752)
To be fair, other platforms and frameworks have had serialization issues, BUT, and this is the big one, they learned from the experience. Will the Ruby community learn? That is the question. Software Engineering are not dirty words!