Re:Why the Latest Rails Exploit Is Indicative of a Bigger Pr...
by tptacek on Thursday February 14, 2013 @01:25PM
(#5220978)
Yes. No other security framework has ever had problems like Rails had. It's definitely not like enterprise Java frameworks that were designed from the outset to satisfy security demands from F-500 appsec teams have had repeated remote code execution flaws. And if they did, they definitely weren't as simple to trigger as "hitting a URL that maps to an embedded Java scripting language". No, only Rails has bugs like these.
[ Parent
| on HN ]
Re:Why the Latest Rails Exploit Is Indicative of a Bigger Pr...
by rambot on Thursday February 14, 2013 @02:15PM
(#5221397)
Where does the post suggest Rails is the only framework with bugs like this? The article opens with: "The latest Rails security flaw is example of a common anti-pattern. ... a similar issue may also exist in Python’s YAML parser ... I am reminded of similar flaws in other frameworks and libraries." I don't think the goal here was to pick on Rails, but to highlight that its recent security woes might be a sign of a bigger common issue.
Re:Why the Latest Rails Exploit Is Indicative of a Bigger Pr...
by tptacek on Thursday February 14, 2013 @02:41PM
(#5221623)
I'm responding to the comment above, not the post.
Re:Why the Latest Rails Exploit Is Indicative of a Bigger Pr...
by ScottBurson on Thursday February 14, 2013 @04:25PM
(#5222450)
I don't read the comment in question as picking on Rails either ("... frameworks like Rails", it says).
Please see my comment downthread.