Re:What The Rails Security Issue Means For Your Startup
by gingerlime on Thursday January 31, 2013 @01:19PM
(#5146390)
Nearly. Both piston and tastypie (the two leading frameworks for writing APIs for django) were affected by a very similar code execution vulnerability a while ago. see https://www.djangoproject.com/weblog/2011/nov/01/piston-and-...
[ Parent
| on HN ]
Re:What The Rails Security Issue Means For Your Startup
by mpyne on Thursday January 31, 2013 @04:11PM
(#5147497)
Those were both third-party modules for Django (albeit popular ones). But at best, this means that Rails devs have known since Nov 2011 or so that YAML code should be carefully audited, especially since there was no equivalent in Ruby for Python's .safe_load (http://stackoverflow.com/questions/14348538/is-there-an-equi...).
I don't mean to beat on the Rails guys too hard though, they're off shipping stuff and I'm not and I'm not very fond of those who criticize while a safe distance from the action. But I think it's fair to say that this could have been foreseen earlier (or much earlier, depending on who you ask).