Live data from Hacker News

Remote Code Execution on a Facebook server

blog.scrt.ch

81–90 of 207 posts

Re: Remote Code Execution on a Facebook server

#82
post #81

The fact that the machine has a hostname "*.thefacebook.com" doesn't imply that it also runs software of the "Facebook" social media software. So not sure how much impact this exploit would have had.

I don't think anyone will ever know how much impact, but it implies that Facebook is not good at security.

Re: Remote Code Execution on a Facebook server

#83
This is why you (looking at frameworks) should never use a format that may contain code to store data, especially when the client has control over that data (even if signed). The same vulnerability has occurred in almost every language/framework that does this, including Rails and Java-based ones. Just use something like JSON, which completely avoids code execution vulnerabilities like this. Except of course for the early JavaScript JSON parsers that just used eval for parsing...

Re: Remote Code Execution on a Facebook server

#84
post #81

The fact that the machine has a hostname "*.thefacebook.com" doesn't imply that it also runs software of the "Facebook" social media software. So not sure how much impact this exploit would have had.

I don't think anyone will ever know how much impact, but it implies that Facebook is not good at security.

I have bad news for you. No one is good at security.

Re: Remote Code Execution on a Facebook server

#85

> scanning an IP range that belongs to Facebook (199.201.65.0/24) ping -4 facebook.com results in 157.240.18.35. Maybe, author used some other way to get those IPs. Can anyone throw a light on this?

Documented on https://developers.facebook.com/docs/sharing/webmasters/craw...

Re: Remote Code Execution on a Facebook server

#86

Wow, a fix in <24 hours, that's pretty impressive.

It took them more than 10 days actually... They just shutdown the instance until they could find a solution.

30.07.2018 00:00 CEST : initial disclosure with every details.

09.08.2018 18:10 CEST : patch in place.

Re: Remote Code Execution on a Facebook server

#87
Some surprising takeaways for me; Facebook uses a Django app in their infrastructure. That app was in debug mode, revealing server secrets. That app was also configured to use the Pickle based session storage, leading to one of the few serious RCE vulnerabilities in Django.

I'll have to remember this next time I think an exploit scenario is too unlikely.

Re: Remote Code Execution on a Facebook server

#89
post #84

Earlier quoted context omitted.

I don't think anyone will ever know how much impact, but it implies that Facebook is not good at security.

I have bad news for you. No one is good at security.

This is great news for me, I work in security :)

Re: Remote Code Execution on a Facebook server

#90

He got $5k for an arbitrary remote execution bug? What a rip-off.

I agree he deserves a higher payout, but it was on a segmented server that seems like it didn't have any customer data or other important data. If he were a real attacker, who knows where else he could've pivoted from this server (perhaps it wasn't quite as segmented as Facebook thought). But assuming it truly was pretty isolated, compromising it probably wouldn't have caused any damage.

Regardless, I feel like he deserves at least $15,000 for this, since it is full RCE.

Post reply on HN