Live data from Hacker News

Beg Bounties (2021)

troyhunt.com

41–50 of 174 posts

Re: Beg Bounties (2021)

#41

Earlier quoted context omitted.

> I don't think security researchers should work for free I agree. The OP comes across a bit gatekeepy to me. Not everyone has made a big name for themselves yet. How are you supposed to find customers in the first place? Gotta start somewhere. Quality of the findings is orthogonal to asking for compensation. There will always be people asking for money without providing value. But I don’t think we should throw the b…

> The OP comes across a bit gatekeepy to me. Hard, hard disagree. I'm glad this "beg bounty" behavior has a name for it, because it's so f'ing obnoxious, and so common, and all it really does is make it that much harder when a serious researcher does need to report a real vulnerability. Let's not pretend there is some sort of gray line between what responsible disclosure looks like, and what bullshit beg bounty discl…

I spent some time working in bounty triage.

This behavior never rose above "mildly annoying". There are a lot of people out there who will check your website for the issues that they know how to find and fire off a form report letting you know.

They are really, really, easy to deal with. There are two major relevant strategies:

- Many programs put it explicitly in their bounty policy that they won't consider the output of an automated tool. This automatically blocks the lowest-effort submissions.

- All programs specify in their policy what they consider a vulnerability and what they don't. "SPF configuration" is a common exclusion.

So if you get a low-value report, it takes maybe one minute to respond with a pointer to the part of your policy that explains why you won't even bother considering the report. If flyby reports are a major issue for you - publish a policy!

(As a third consideration, for me personally, these reports were especially easy to handle because you'd see the same guy filing more or less identical reports to several programs, and after the first time, you'd already have a good understanding of exactly what the report was saying.)

The people filing these reports are doing valuable work. Some programs really do care about some of the issues they find. Most programs don't care about most of the issues - but you can hardly blame the researcher for finding out whether the issue they already have in their hand might be worth something.

When I saw the headline, I thought of a different phenomenon that bothered me more. Many researchers are very ...anxious... about the status of their reports. I saw one guy, apparently from Egypt, who regularly found real vulnerabilities in a major website and earned thousands of dollars a month in bounties. If a report came in from him, it got taken seriously.

But he was constantly asking for status updates and commitments on when a report might get paid out. This was unpleasant to deal with. On the other hand, I did also see a handful of reports fall through the cracks and go untouched for months at a time, so again it's hard to blame the guy too much.

Re: Beg Bounties (2021)

#42

I’m less upset about people begging for bounties than I am learning that leaking children’s voice recordings isn’t an instant deathblow to a company.

Why would it be? Say you film your kid's birthday party and put it up on youtube. You just leaked voice recordings of a lot of other children. What's the harm supposed to be?

Re: Beg Bounties (2021)

#43
post #16

I don't really understand the point of making a big stink about Beg Bounty Hunters. They're invariably people in developing countries, for whom occasional SPF or Clickjacking payouts will be meaningful. And there's an unbounded supply of them. They're not going away. All you can control is the way you respond to them; lashing out at them in public seems like a pretty unhealthy response. Not for them; who cares? There…

[flagged]

first time i've heard of this merch thing... sources?

Re: Beg Bounties (2021)

#44

e: I just noticed, this post was from 2 years ago. It should have (2021) in the header. --- I help run a bug bounty program, we get a lot of submissions. Way too many of them are zero or low effort. The SPF meme one definitely resonates with me, we get it a whole lot. Occasionally we will get someone who submits a half dozen variations of the same zero/low-effort report. When we turn around and deny them all (because…

Here is another perspective:

I have been making money through bug bounties for the past 5 years (I'm a researcher on the major bug bounty sites and multiple private ones).

More times than I can count, I have found major, non-low effort bugs, and the company will spend time deflecting, and I just won't end up getting paid. Luckily, this is less than 10% of the valid bugs I've found. I've learned to just move on after a certain point.

This behavior from these companies nearly made me quit 2 years ago. I was so frustrated that I completely stopped for 6 months.

I found 50 bugs in a week for one major company and they spend 2 months trying to tell me that they don't own the site anymore, and weren't going to pay me. It was in scope at the time I found the bugs. These weren't just minor bugs either. It allowed me to break into all private rooms on the service in multiple ways, get access to back-end network settings, and even takeover accounts.

I pushed back and they were in violation of their SLA. I got a nice payout a few weeks later.

Re: Beg Bounties (2021)

#45

I’m less upset about people begging for bounties than I am learning that leaking children’s voice recordings isn’t an instant deathblow to a company.

Why would it be? Say you film your kid's birthday party and put it up on youtube. You just leaked voice recordings of a lot of other children. What's the harm supposed to be?

Feel like recording intimate moments like that should just about be a crime at this point. Sick of every dicknose with an iPhone trying to "remember" a group dinner

Re: Beg Bounties (2021)

#46
post #16

I don't really understand the point of making a big stink about Beg Bounty Hunters. They're invariably people in developing countries, for whom occasional SPF or Clickjacking payouts will be meaningful. And there's an unbounded supply of them. They're not going away. All you can control is the way you respond to them; lashing out at them in public seems like a pretty unhealthy response. Not for them; who cares? There…

This is extortion, and a crime.

Re: Beg Bounties (2021)

#47
post #7

Earlier quoted context omitted.

my favourite is "your docker registry is publicly accessible" yeah man, i know that. i made it public. i eventually had to take it down, just to stop the flood of beg bounties telling me about it.

Oh yeah... I don't run a docker registry, but Amazon feels it necessary to remind me periodically that FreeBSD releases are public AMIs, and their filesystem images are public, and I have publicly readable data in S3 (which is mandatory in order to create an AWS Marketplace listing). So much "yes I know it's supposed to be that way".

It’s so bizarre that every time I upload something to S3 I have to jump through a hoop to make it publicly readable and Amazon displays a massive warning sign.

Like the only thing I use S3 for is hosting open source software binaries. Maybe there’s a use case for restricting access, but I don’t even know what that would be.

Re: Beg Bounties (2021)

#48

I’m less upset about people begging for bounties than I am learning that leaking children’s voice recordings isn’t an instant deathblow to a company.

Why would it be? Say you film your kid's birthday party and put it up on youtube. You just leaked voice recordings of a lot of other children. What's the harm supposed to be?

As of 2013, COPPA specifically defines recordings of a child's voice as a type of "personal information" about the child; as a result, operators of online services "directed at children" are required to get parental consent to collect that information, and are required to protect it appropriately.

https://www.ftc.gov/news-events/news/press-releases/2012/12/...

Re: Beg Bounties (2021)

#49

Earlier quoted context omitted.

Oh yeah... I don't run a docker registry, but Amazon feels it necessary to remind me periodically that FreeBSD releases are public AMIs, and their filesystem images are public, and I have publicly readable data in S3 (which is mandatory in order to create an AWS Marketplace listing). So much "yes I know it's supposed to be that way".

It’s so bizarre that every time I upload something to S3 I have to jump through a hoop to make it publicly readable and Amazon displays a massive warning sign. Like the only thing I use S3 for is hosting open source software binaries. Maybe there’s a use case for restricting access, but I don’t even know what that would be.

Inadvertent public buckets leading to data loss is what created those hoops. Trying to take the ammo out of the footgun.

https://www.theregister.com/2022/12/14/aws_simple_storage_se...

Re: Beg Bounties (2021)

#50

Earlier quoted context omitted.

Why would it be? Say you film your kid's birthday party and put it up on youtube. You just leaked voice recordings of a lot of other children. What's the harm supposed to be?

Feel like recording intimate moments like that should just about be a crime at this point. Sick of every dicknose with an iPhone trying to "remember" a group dinner

Before we make it a crime, should we have a theory of the harm it inflicts?
Post reply on HN