{"id":4058,"date":"2016-01-28T02:12:37","date_gmt":"2016-01-27T18:12:37","guid":{"rendered":"https:\/\/www.darknet.org.uk\/?p=4058"},"modified":"2016-01-28T02:12:58","modified_gmt":"2016-01-27T18:12:58","slug":"paypal-remote-code-execution-vulnerability-patched","status":"publish","type":"post","link":"https:\/\/www.darknet.org.uk\/2016\/01\/paypal-remote-code-execution-vulnerability-patched\/","title":{"rendered":"PayPal Remote Code Execution Vulnerability Patched"},"content":{"rendered":"

So this is a big one, and thankfully this PayPal Remote Code Execution Vulnerability was discovered by security researchers and not the bad guys. Although there’s no way for us to know if someone has been using this to siphon data out of PayPal for some time before the whitehats found it.<\/p>\n

\"PayPal<\/p>\n

It’s a roundabout bug that turns out serious, and why I tell developers don’t mess with serialised data – it’s ugly. In this case object deserialisation in Java basically allowed for remote command execution on PayPal servers.<\/p>\n

Independent security researcher Michael Stepankin has reported a since-patched remote code execution hole in Paypal that could have allowed attackers to hijack production systems.<\/p>\n

The critical vulnerability affecting manager.paypal.com revealed overnight was reported 13 December and patched soon after disclosure.<\/p>\n

It allowed Stepankin to execute arbitrary shell commands on PayPal web servers through Java object deserialisation opening access to production databases.<\/p>\n

“I immediately reported this bug to PayPal security team and it was quickly fixed after that,” Stepankin says<\/p>\n

“While security testing of manager.paypal.com, my attention was attracted by unusual post form parameter \u201coldFormData\u201d that looks like a complex object after base64 decoding.<\/p><\/blockquote>\n