MIT Bug Finder Uncovers Flaws In Web Apps In 64 Seconds (csoonline.com)
itwbennett quotes a report from CSO: A new tool from MIT exploits some of the idiosyncrasies in the Ruby on Rails programming framework to quickly uncover new ones, writes Katherine Noyes. In tests on 50 popular web applications written using Ruby on Rails, the system found 23 previously undiagnosed security flaws, and it took no more than 64 seconds to analyze any given program. Ruby on Rails is distinguished from other frameworks because it defines even its most basic operations in libraries. MIT's researchers took advantage of that fact by rewriting those libraries so that the operations defined in them describe their own behavior in a logical language.
Quick, everyone! Use this tool and collect bug bounties before they're all gone.
From what I can tell, it seems like it might be something like a code analysis tool that swapped in a logger to profile methods called along with some metadata (time spent in subroutine, etc).
http://open.blogs.nytimes.com/2008/03/05/the-new-york-times-perl-profiler/?_r=0
BUT ON AN APP!
or am i missing something?
MIT's researchers took advantage of that fact by rewriting those libraries so that the operations defined in them describe their own behavior in a logical language.
The summary seems to imply that this would notify other people of vulnerabilities, but it's actually something that requires full source code access; it sits between your code and the rails library, trying to figure out whether you're doing something problematic or not. Useful to developers, in that it can uncover bugs they added.
One important thing to keep in mind about Rust is that it has attracted some people who were notable Rubyists in the past. They jumped ship when the Ruby on Rails hype started really dying down a few years ago, once more and more people finally clued in and realized that Ruby and Rails are often problematic.
If prominent Ruby software like Ruby on Rails has this many flaws, why should we believe that Rust, if it's being developed by former Rubyists, won't suffer from similar problems?
the biggest flaw was that they were written in Ruby on Rails.
Anons need not reply. Questions end with a question mark.
Gone in 64 seconds.
how long did it take to rewrite the libraries?
Many "cool and new" technologies started out with a rather dismissive and arrogant attitude towards predecessors — only to then encounter the same problems as other did before and have to solve them in a hurry, shooting yourself in the same extremity (with the same gun), and stepping on the same rake.
From my experience, Ruby is especially bad at it. Release 1.9.2 not quite compatible with 1.9.1? What?!
Published packages ("gems") not signed. Huh?
So, when I hear about yet another problem in that world, all I can do is shrug...
In Soviet Washington the swamp drains you.
You're absolutely right. I think we're seeing the same thing happening with Rust. It's pretty much the new Ruby. So many Rustacean (yes, that is what they prefer to be called, believe it or not) ridicule C++ constantly. Yet we find that Rust isn't any better than C++, and Rust is actually often a whole lot worse! Rust's syntax makes C++'s look nice. Rust's semantics make C++'s easy to comprehend. Rust's standard library makes C++'s look like a work of fine art. Rust's ownership system makes C++'s RAII and smart pointers seem pleasant to use. The kids pushing Rust don't realize that the problems they're "solving" were already solved years, if not decades, ago by C++.
Can't find the tool....
Python and Ruby are similar languages, and yet the cultures around the two are very different. A certain segment of Ruby has moved to node.js now.
https://www.youtube.com/watch?...
http://rareformnewmedia.com/