Live data from Hacker News

The easiest bug bounties I have won

josipfranjkovic.blogspot.com

21–29 of 29 posts

Re: The easiest bug bounties I have won

#21
post #5

Doesn't this show just how crappy the backend permissions must be in Facebook's code? Every new page needs to get the permissions checks exactly right, otherwise... Disaster. As an analogy, It's like the most stupidly-designed UNIX system, where each user program that opens a file runs as root and must remember to do a permissions check when opening a file, rather than centralising the permissions system in the kerne…

This is probably a symptom of the number of people employed at Facebook, lack of documentation, and that the entire app and related infrastructure is a (quickly) moving target.

Re: The easiest bug bounties I have won

#22
post #5

Doesn't this show just how crappy the backend permissions must be in Facebook's code? Every new page needs to get the permissions checks exactly right, otherwise... Disaster. As an analogy, It's like the most stupidly-designed UNIX system, where each user program that opens a file runs as root and must remember to do a permissions check when opening a file, rather than centralising the permissions system in the kerne…

[deleted]

Re: The easiest bug bounties I have won

#23
post #3

It is quite saddening that there is a recent trend of hiding the complete URL from the user when the URL itself conveys much information. When the URL is hidden the user is not given the incentive to look at the URL, let alone modify it. This kind of bug should have been discovered much sooner when the user is given the opportunity to directly look at the URL and experiment with it.

>experiment with it Be careful with simple "experimentation" like this. You can fall afoul of the CFAA for exactly this.

Explain?

Re: The easiest bug bounties I have won

#24

Earlier quoted context omitted.

>experiment with it Be careful with simple "experimentation" like this. You can fall afoul of the CFAA for exactly this.

Explain?

This is very similar to what Weev was indicted and convicted for.[0] Simply passing valid requests to a system can by construed as "unauthorized" if it is unexpected by the operator of that system.

[0] https://en.wikipedia.org/wiki/Goatse_Security

Re: The easiest bug bounties I have won

#25
post #5

Doesn't this show just how crappy the backend permissions must be in Facebook's code? Every new page needs to get the permissions checks exactly right, otherwise... Disaster. As an analogy, It's like the most stupidly-designed UNIX system, where each user program that opens a file runs as root and must remember to do a permissions check when opening a file, rather than centralising the permissions system in the kerne…

Facebook's permissions model is very complex. Just imagine a case where Fanny comments on Alice's photo which is shared to a custom friends list, which contains Bert (Alice's friend), who Fanny put on her block list... and that's a simple example.

It has been proposed a number of times to put it all behind an API. I do not know if this has been finished yet. I remember an epic diff comment thread which only ended after the author defended her solution with a mathematical proof of correctness.

Re: The easiest bug bounties I have won

#26
post #25
post #5

Doesn't this show just how crappy the backend permissions must be in Facebook's code? Every new page needs to get the permissions checks exactly right, otherwise... Disaster. As an analogy, It's like the most stupidly-designed UNIX system, where each user program that opens a file runs as root and must remember to do a permissions check when opening a file, rather than centralising the permissions system in the kerne…

Facebook's permissions model is very complex. Just imagine a case where Fanny comments on Alice's photo which is shared to a custom friends list, which contains Bert (Alice's friend), who Fanny put on her block list... and that's a simple example. It has been proposed a number of times to put it all behind an API. I do not know if this has been finished yet. I remember an epic diff comment thread which only ended aft…

> I remember an epic diff comment thread which only ended after the author defended her solution with a mathematical proof of correctness.

Can you share anything more about this anecdote? I feel like there's a really interesting story there.

Re: The easiest bug bounties I have won

#27
post #25

Earlier quoted context omitted.

Facebook's permissions model is very complex. Just imagine a case where Fanny comments on Alice's photo which is shared to a custom friends list, which contains Bert (Alice's friend), who Fanny put on her block list... and that's a simple example. It has been proposed a number of times to put it all behind an API. I do not know if this has been finished yet. I remember an epic diff comment thread which only ended aft…

> I remember an epic diff comment thread which only ended after the author defended her solution with a mathematical proof of correctness. Can you share anything more about this anecdote? I feel like there's a really interesting story there.

Not a lot that's public, but Mary P commented on this AMA:

https://www.reddit.com/r/IAmA/comments/1ydy0w/i_am_raylene_y...

Re: The easiest bug bounties I have won

#28
post #3

It is quite saddening that there is a recent trend of hiding the complete URL from the user when the URL itself conveys much information. When the URL is hidden the user is not given the incentive to look at the URL, let alone modify it. This kind of bug should have been discovered much sooner when the user is given the opportunity to directly look at the URL and experiment with it.

It's not too hard to obfuscate the actual domain for non-technical users, leading to easier phishing. By only displaying the actual domain name, it's much easier for people to see that they aren't on the site they expect to be.

IMO, the tradeoff of reducing phishing effectiveness is worth the small amount of additional effort needed to find this bug.

Re: The easiest bug bounties I have won

#29

I've been wanting to start doing bug bounties for a while now, but I have only been able to find serious bugs in sites without bug bounty schemes. I was starting to think that it would be impossible to get any bug bounties because of the number of people searching, but this post gives me some confidence.

New programs are launching all the time or the scope of current programs is expanding out to include new products or features. It's never too late to get started, there's actually more work than researchers at the moment and it will be like that for many, many years to come.

In terms of how to get started, I definitely suggest monitoring the various bug bounty sites to see what's new and if a bounty's scope has expanded.

There's also a bunch of guides, tutorials, and tools listed on Bugcrowd's Forum: https://forum.bugcrowd.com/c/security-research

Post reply on HN