4 ms·

So what is the exploit, and how do we fix it?

• ainsleyb 14y ago
  I've posted a little bit more on our blog at: http://blog.tinfoilsecurity.com/use-rails-check-yourself-for-the-yaml-exploit http://blog.tinfoilsecurity.com/use-rails-check-yourself-for...
• patio11 14y ago
  There have been multiple vulnerabilities discovered with semi-related causes. These all have (several) exploits which are widely available. The upshot is that they permit remote code execution (i.e. "root the server") on virtually all Rails applications accessible on the public Internet and, perhaps, some which are not. Rails has been updated to close these particular vulnerabilities. The proper versions are listed in these two advisories. There are also work-arounds if your app is not in a state to just upgrade Rails. If your app is in that state, I strongly advise you that your only priority for the next several days is fixing that, because one should have high confidence that there will be more vulnerabilities announced soonish. https://groups.google.com/forum/?fromgroups=#!topic/rubyonrails-security/1h2DR63ViGo https://groups.google.com/forum/?fromgroups=#!topic/rubyonra... https://groups.google.com/forum/?fromgroups=#!topic/rubyonrails-security/61bkgvnSGTQ https://groups.google.com/forum/?fromgroups=#!topic/rubyonra...
• px43 14y ago
  This is about the equivalent of putting a single quote in a GET variable to detect sql injection. It tries to detect any bugs in the bug class, rather than a specific bug. The solution is different depending on what component is broken.