News for hackers. Stuff that matters.
Re:Metasploit Rails 3 Remote Code Execution Hours Away by kapilkale on Thursday January 10, 2013 @12:48AM (#5035681)
I'm unable to reproduce- not sure why. Seeing no parameters. I'm getting:

  Started POST "/user/sign_in" for 127.0.0.1 at 2013-01-09 21:40:56 -0800
  Processing by UsersController#sign_in as */*
If I comment out the patch, I see:

  Parameters: {"secret"=>1969-12-31 16:00:00 -0800}
So I suspect others may not see the same exception... I'm using ActiveSupport 3.0.3, fyi.
Re:Metasploit Rails 3 Remote Code Execution Hours Away by gautamc on Thursday January 10, 2013 @01:10AM (#5035747)
Yep. I see what you mean.

activesupport-3.2.11/lib/active_support/core_ext/hash/conversions.rb has a -- DISALLOWED_XML_TYPES = %w(symbol yaml) -- which is used by its def typecast_xml_value to raise the exception.

I don't see these lines of code in activesupport-3.0.3/lib/active_support/core_ext/hash/conversions.rb

In my case I could upgrade to 3.2.11.

In your case, I am guessing you added the lines of code that disable xml and yaml parameter parsing to an initializer (or application.rb). This way, activesupport simply wouldn't try to convert the parameter value in question into a ruby object.

Re:Metasploit Rails 3 Remote Code Execution Hours Away by kapilkale on Thursday January 10, 2013 @01:31AM (#5035805)
Right. Thanks!