Ruby On Rails SQL Injection Flaw Has Serious Real-Life Consequences
vikingpower writes "As a previous Slashdot story already reported, Ruby on Rails was recently reported to suffer from a major SQL injection flaw. This has prompted the Dutch government to take the one and only national site for citizens' digital identification offline (link in Dutch, Google translation to English). Here is the English-language placeholder page for the now-offline site. This means that 16 million Dutch citizens cannot authenticate themselves anymore with government instances, and that those same government instances can not communicate anything to those same citizens anymore."
Fixes were released, so it looks like it's on their sysadmin team now.
Should have used ASP.NET
That's just silly, since the fix can be easily applied. It really nothing compared to all the wordpress exploits out the that never get patched.
You know, it's pretty obvious that you're trolling, but there's a real question here:
Why would we use frameworks, given that they have security bugs coming up all the time?
Answer: Because code people write themselves isn't any less buggy, and with a framework, at least you have other people looking for bugs too.
My blog: http://www.seebs.net/log/ --- My iPhone/iPad app: http://www.seebs.net/seebsfrac/
Why is a toy programming environment like Ruby on Rails used for such a critical infrastructure?
This vector that's been described doesn't work unless the attacker has the HMAC that's signing the session cookie.
That was last week. This time attackers can bypass authentication systems, inject arbitrary SQL, inject and execute arbitrary code, or perform a DoS attack. Please try to keep up.