Re:Hacking Facebook’s Legacy API, Part 1: Making Calls on Be...
by neilwillgettoit on Tuesday July 08, 2014 @04:48PM
(#8006662)
As a security researcher, the most impressive part of this is the response timeline from Facebook's security team. 3~ hours from first report to temporary patch! That's insane.
[ Parent
| on HN ]
Re:Hacking Facebook’s Legacy API, Part 1: Making Calls on Be...
by eugenez on Tuesday July 08, 2014 @07:19PM
(#8007279)
We also have a system for patching vulnerabilities which does not require a full code push. It has been useful on a number of occasions. (source: I patched this one)
Re:Hacking Facebook’s Legacy API, Part 1: Making Calls on Be...
by stevenh on Tuesday July 08, 2014 @07:27PM
(#8007309)
Does Facebook usually respond to exploit reports so quickly, or does the fact that the discoverer (Stephen Sclafani) helped Facebook find bugs in previous years mean that his emails were automatically flagged as high-priority?
Re:Hacking Facebook’s Legacy API, Part 1: Making Calls on Be...
by eugenez on Tuesday July 08, 2014 @07:39PM
(#8007342)
We try to respond to any exploit of this severity immediately, and will often disable a feature temporarily while working on a fix rather than letting the exploit remain open. It helps a lot when the repro steps are as clear as they were in this one.
Re:Hacking Facebook’s Legacy API, Part 1: Making Calls on Be...
by aristus on Tuesday July 08, 2014 @05:29PM
(#8006837)
Facebook deploys code twice a day. It used to be once a day but as the org grew they decided to double down. They can deploy even more often if there's a "pusher i haz a hotfix" situation like this.