Re:Security Announcement for Devise (Rails authentication so...
by benmmurphy on Monday January 28, 2013 @03:33PM
(#5130476)
This bug looks similar to the previous rails SQL injection/manipulation issues. The code expects some type T but instead gets a type U and because of this some unexpected behaviour happens. In a typesafe language this mistake would be harder to make. This is a really ugly one to solve and there is going to be lots of rails code bases that are going to be vulnerable to this issue. Maybe there is an option in mysql or the vulnerable databases to treat this as an error rather than generate a warning.
if you don't have anything that is enforcing types then you are fucked :) it is ok to have untyped (or weakly typed) db and statically typed frontend. it is ok to have typed db and dynamically typed frontend. but if you have untyped db and dynamically typed frontend you are in for a world of pain.
Re:Security Announcement for Devise (Rails authentication so...
by joernchen on Monday January 28, 2013 @12:20PM
(#5129409)
This very much is true. I'll put some details up soon.
Re:Security Announcement for Devise (Rails authentication so...
by slowpoison on Monday January 28, 2013 @03:19PM
(#5130415)
Can you please link to the remote execution bug?
Re:Security Announcement for Devise (Rails authentication so...
by tedunangst on Monday January 28, 2013 @03:57PM
(#5130588)
If this is the bug I think it is (from following joernchen), it has a lot more to do with the "MySQL is terrible" post from a few days back than it does with Rails/Devise.
The recent remote code execution bug was so bad that I think it is in fact legit to worry about how many people had been running around with it months or years before disclosure.