News for hackers. Stuff that matters.
Re:Facebook vulnerability 2013 by tptacek on Saturday August 17, 2013 @10:46PM (#6231405)
They can't pay people to violate their terms of use or to try to violate the privacy of their users. Even if they wanted to, they're probably not allowed to do that.
Re:Facebook vulnerability 2013 by spyder on Sunday August 18, 2013 @03:40AM (#6232009)
So if a security bug was discovered using methods that are against the TOS then the information about the bug is worthless for them and it's better to sold it elsewhere.
Re:Facebook vulnerability 2013 by goblin89 on Sunday August 18, 2013 @09:10AM (#6232571)
The whitehat page explicitly says that you must “not interact with other accounts without the consent of their owners” in order to qualify for the bounty. So yes, apparently Facebook can deny payment and suspend your account if they can reasonably suspect that you violated someone's privacy during bug discovery.

However, it seems that if you don't give them any clues in your report, they'll close their eyes and won't investigate carefully that possibility.

Re:Facebook vulnerability 2013 by Udo on Sunday August 18, 2013 @06:04AM (#6232239)
An argument could be made it wasn't so much the discovery of the bug but rather the manner of reporting it that was a ToS violation.
Re:Facebook vulnerability 2013 by hrjet on Sunday August 18, 2013 @10:59AM (#6232828)
The payment would ofcourse be for discovering the bug.
Re:Facebook vulnerability 2013 by toomuchtodo on Monday August 19, 2013 @01:07PM (#6238281)
Good point.

Lesson learned: Find a security hole, report it to Facebook, and they don't respond after two attempts? Sell it as a zero day.

Incentives matter. And there is always money to be had somewhere else.

Re:Facebook vulnerability 2013 by drewcrawford on Sunday August 18, 2013 @02:24PM (#6233586)
Well according to Facebook, "this is not a bug". Which means the feature works as intended. If he is using Facebook as it is intended, then how can he be breaking the TOS?

When an employee whose job it is to evaluate security issues says "this is not a bug", that determination carries the force of law the same way as if it appeared in the TOS. You cannot rely on people to follow some nebulous "spirit of the TOS" when meanwhile your employees have already made a contrary specific determination for how it applies to this particular bug.

Re:Facebook vulnerability 2013 by loceng on Saturday August 17, 2013 @11:06PM (#6231458)
They wouldn't paying him to violate the terms ... and it's not like Facebook has any problem with changing a user's privacy settings without permission - except I guess we probably somewhere in the agreements agreed to allow that, or not hold them accountable - probably both..
Re:Facebook vulnerability 2013 by walid on Tuesday August 20, 2013 @05:29AM (#6242593)
hahaha funny point
Re:Facebook vulnerability 2013 by TheNewAndy on Sunday August 18, 2013 @03:03PM (#6233734)
Creating a test account is also kind of a violation of the TOS anyway:

"You will not provide any false personal information on Facebook, or create an account for anyone other than yourself without permission.

You will not create more than one personal account."

Re:Facebook vulnerability 2013 by jtdowney on Sunday August 18, 2013 @03:21PM (#6233795)
They specifically allow accounts to be created for whitehat purposes at https://www.facebook.com/whitehat/accounts/
Re:Facebook vulnerability 2013 by alxndr on Monday August 19, 2013 @02:41AM (#6235950)
Interestingly, from that page:

"Please use a test account instead of a real account when investigating security vulnerabilities. When you are unable to reproduce a security vulnerability with a test account, it is acceptable to use a real account, except for automated testing."