Facebook Ignores Hacker's Bug Report, Then Refuses to Pay Him
August 19, 2013 2:03 PM
comment(s) - last by
Popular social network claims hacker's poor English language skills disqualify him from receiving an award
Social networking giant Facebook, Inc. (
) is mired in a new controversy, this time dealing with
bugs in its network and their privacy ramifications
I. "This is Not a Bug"
The story begins with a Palestinian information systems expert named
who last week discovered a bug in the social network that allowed him to post to anyone's wall -- including those he wasn't friends with. This is a pretty big deal as one of Facebook's
key curbs to spammers
is that you must be friends with people, by default, to post to their walls (and users can even further limit their walls so that only certain close friends can post, with the right settings tweaks).
He filed the bug report to the proper channel --
-- hoping to get paid. But a Facebook engineer replied to him that when they clicked the link they only got an error:
Frustrated, he sent another bug report, only to be told by Facebook Security Engineer "Emrakul", "I am sorry this is not a bug."
So the security researcher took matters into his own hands posting on a user's wall that he knew would draw attention -- Facebook CEO Mark Zuckerberg. He wrote in a friendly tone, providing a PasteBin to a detailed log of his interactions with Facebook engineers via a bug report system:
II. Okay, Maybe it
The post certainly attracted attention. Within minutes he was contacted by a security team member, Facebook engineer
. But Facebook didn't exactly greet his disclosure with open arms. The company suspended his account temporarily for posting on Zuck's wall.
While they eventually reinstated his account, Facebook ultimately refused to pay the $500 USD bounty that a bug report typically carries.
-- a Facebook engineer -- defends this decision in a Ycombinator forums post, first offering a roundabout jab at the reporter's English, commenting:
For background, as a few other commenters have pointed out, we get hundreds of reports every day. Many of our best reports come from people whose English isn't great - though this can be challenging, it's something we work with just fine and we have paid out over $1 million to hundreds of reporters. However, many of the reports we get are nonsense or misguided, and even those (if you enter a password then view-source, you can access the password! When you submit a password, it's sent in the clear over HTTPS!) provide some modicum of reproduction instructions. We should have pushed back asking for more details here.
There will be no pay day for Mr. Khalil from Facebook. [Image Source: Zagg]
Mr. Jones goes on to write:
As you can see at
, in order to qualify for a payout you must "make a good faith effort to avoid privacy violations" and "use a test account instead of a real account when investigating bugs. When you are unable to reproduce a bug with a test account, it is acceptable to use a real account, except for automated testing. Do not interact with other accounts without the consent of their owners." Unfortunately, the OP did neither of those things. We welcome and will pay out for future reports from him (and anyone else!) if they're found and demonstrated within these guidelines.
But that argument is clearly flawed, in that Facebook's staff had told him "this is not a bug". As one commenter on Mr. Khalil's blog puts it:
They told him flat out when he reported it "this is not a bug" they didn't ask for more info or anything. He post on zuck's page then it becomes a bug but he violated TOS.. That's a no win right there.
Mr. Jones did offer this halfhearted apology:
To be clear, we fixed this bug on Thursday. The OP is correct that we should have asked for additional repro instructions after his initial report. Unfortunately, all he submitted was a link to the post he'd already made (on a real account whose consent he did not have - violating our ToS and responsible disclosure policy), saying that "the bug allow facebook users to share links to other facebook users". Had he included the video initially, we would have caught this much more quickly.
But so far there's been no indication that Facebook is willing to dish out the $4,000 it normally gives for severe bug reports.
III. Facebook is Setting a Dangerous Precedent With Response
has been started to pay Mr. Khalil the amount that Facebook shorted him, considering he did disclose in a relatively responsible way a bug which could have brought him big cash from spammers.
The whole experience can be viewed as a cautionary tale to security experts -- particularly foreign ones. While Facebook has indeed paid out $1M+ USD for bug reports (the equivalent of 2,000 smaller bugs which offer a $500 bounty, or 250 bigger ones), it also at times has refused to acknowledge certain bugs or arbitrarily denied reporters their bounties. These scenarios will certainly drive some to full disclosure out of frustration, although few full disclosures will be as flashy or carefully documents as Mr. Khalil's.
Facebook can choose not to pay researchers, but it must beware alienating the community. [Image Source: Getty Images/modifications Jason Mick]
Yes, Mr. Khalil could be interpreted to be in violation of Facebook's ToS. But it's a black eye to the security program to not pay him, when he kept details of the vulnerability private, acted politely throughout the entire disclosure, and even first tried to go through official channels. It's Facebook's decision not to pay him, but it's the kind of decision that may cost the company in the long run, by stifling responsible disclosure.
It should be noted this is not the first time a bug has been applied at Mark Zuckerberg's Facebook account. Previously, a bug had
outed his private photos
, revealing his budding romance with Priscilla Chan and his passion for hunting -- which in turn gave rise to the "
Kill what you eat
Khalil on Blogspot
Facebook on Ycombinator
Reward Khalil on IndieGogo
This article is over a month old, voting and posting comments is disabled
RE: 500-4000$ ????
8/20/2013 8:40:13 AM
They're striking this guy by being overly strict. He obviously intended no harm, tried to report it, and finally went for the CEO. His honest persistence should be rewarded.
Sure, his English is not great, and he technically broke the FB terms in not using test accounts, but you can scratch that off due to ignorance.
Man deserves his $500. It was an extremely significant vulnerability.
"It looks like the iPhone 4 might be their Vista, and I'm okay with that." -- Microsoft COO Kevin Turner
Quick Note: Facebook Unveils Year-Long Data Breach of User Phone Numbers, Email Addresses
June 24, 2013, 10:54 AM
Facebook Bug Reveals Zuckerberg's Private Photos
December 6, 2011, 9:07 PM
Facebook Wins $873M Judgment Against Spammer
November 26, 2008, 9:03 AM
Retiree Sues Apple For $7,500 for Wiping Honeymoon Photos From His iPhone
November 30, 2015, 10:23 AM
iPhone 7 May Pack 3-4 GB Memory, More Storage; 4-Inch Comeback is Rumored
November 20, 2015, 10:12 PM
OnePlus One, OnePlus 2 Will Receive Android Marshmallow in Q1 2016
November 16, 2015, 9:58 AM
Lenovo Whoa: Motorola Droid MAXX 2 and Turbo 2 Break Cover in Leaks
October 26, 2015, 3:12 PM
Leak: Apple Preps for First Real Android App Foray With New Apple Music App
October 24, 2015, 1:59 PM
Pepsi Smartphone? Empty Calories Coming Soon to the Midrange
October 12, 2015, 11:41 PM
Most Popular Articles
Top 5 Smart Watches
July 21, 2016, 11:48 PM
Free Windows 10 offer ends July 29th, 2016: 10 Reasons to Upgrade Immediately
July 22, 2016, 9:19 PM
Latest Blog Posts
Sceptre Airs 27", 120 Hz. 1080p Monitor/HDTV w/ 5 ms Response Time for $220
Dec 3, 2014, 10:32 PM
Costco Gives Employees Thanksgiving Off; Wal-Mart Leads "Black Thursday" Charge
Oct 29, 2014, 9:57 PM
"Bear Selfies" Fad Could Turn Deadly, Warn Nevada Wildlife Officials
Oct 28, 2014, 12:00 PM
The Surface Mini That Was Never Released Gets "Hands On" Treatment
Sep 26, 2014, 8:22 AM
ISIS Imposes Ban on Teaching Evolution in Iraq
Sep 17, 2014, 5:22 PM
More Blog Posts
Copyright 2016 DailyTech LLC. -
Terms, Conditions & Privacy Information