Live data from Hacker News

cURL removes bug bounties

etn.se

41–50 of 271 posts

Re: cURL removes bug bounties

#41
What I wonder is if this will actually reduce the amount of slop.

Bounties are a motivation, but there's also promotional purposes. Show that you submitted thousands of security reports to major open source software and you're suddenly a security expert.

Remember the little iot thing that got on here because of a security report complaining, among other things, that the linux on it did not use systemd?

Re: cURL removes bug bounties

#42
post #9

It seems open source loses the most from AI. Open source code trained the models, the models are being used to spam open source projects anywhere there's incentive, they can be used to chip away at open source business models by implementing paid features and providing the support, and eventually perhaps AI simply replaces most open source code

"open source" and "business model" in the same sentence... next you're gonna tell me to eat pudding with a fork.

Just leaving this here: https://en.wikipedia.org/wiki/Pudding_mit_Gabel

Re: cURL removes bug bounties

#43
post #9

It seems open source loses the most from AI. Open source code trained the models, the models are being used to spam open source projects anywhere there's incentive, they can be used to chip away at open source business models by implementing paid features and providing the support, and eventually perhaps AI simply replaces most open source code

> they can be used to chip away at open source business models by implementing paid features and providing the support

There are a lot of things to be sad about AI, but this is not it. Nobody has a right to a business model, especially one that assumes nobody will compete with you. If your business model relies on the rest of the world bring sucky so you can sell some value-added to open-core software, i'm happy when it fails.

Re: cURL removes bug bounties

#44
post #11
post #2

A list of the slop if anyone is interested: https://gist.github.com/bagder/07f7581f6e3d78ef37dfbfc81fd1d...

I looked at two reports, and I can’t tell if the reports are directly from an ai or some very junior student not really understanding security. LLms to me sound generally more convincing.

Some (most?) are llm chat copy paste addressing non existing users in conversations like [0] - what a waste of time.

[0] https://hackerone.com/reports/2298307

Re: cURL removes bug bounties

#46
post #41

What I wonder is if this will actually reduce the amount of slop. Bounties are a motivation, but there's also promotional purposes. Show that you submitted thousands of security reports to major open source software and you're suddenly a security expert. Remember the little iot thing that got on here because of a security report complaining, among other things, that the linux on it did not use systemd?

I dont think bounties make you an "expert". If you want to be deemed an expert, write blogs detailing how the exploit works. You can do that without a bounty.

In many ways one of the biggest benefits of bug bounties is having a dedicated place where you can submit reports and you know the person on the other end wants them and isn't going to threaten to sue you.

For the most part, the money in a bug bounty isn't work the effort needed to actually find stuff. The exception seens to be when you find some basic bug, that you can automate scan half the internet and submit to 100 different bug bounties.

Re: cURL removes bug bounties

#47
post #18

An entry fee that is reimbursed if the bug turns out to matter would stop this, real quick. Then again, I once submitted a bug report to my bank, because the login method could be switched from password+pin to pin only, when not logged in, and they closed it as "works as intended", because they had decided that an optional password was more convenient than a required password. (And that's not even getting into the di…

> An entry fee that is reimbursed if the bug turns out to matter would stop this, real quick. The problem is that bug bounty slop works . A lot of companies with second-tier bug bounties outsource triage to contractors (there's an entire industry built around that). If a report looks plausible, the contractor files a bug. The engineers who receive the report are often not qualified to debate exploitability, so they j…

Triage gets outsourced because the quality of reports is low.

If filing a bad report costs money, low quality reports go down. Meanwhile anyone still doing it is funding your top notch security team because then they can thoroughly investigate the report and if it turns out to be nothing then the reporter ends up paying them for their time.

Re: cURL removes bug bounties

#48
post #27
post #23

Earlier quoted context omitted.

That anecdote is hilarious and scary in equal measures. Optional passwords are certainly more convenient than required ones, but so are optional PINs. The most convenient UX would be never needing to log in at all! Unless you find it inconvenient for others to have access to your bank account of course

I really hate the current trend of not having passwords. For example perplexity doesn't have a password, just an email verification to login.

I hate this as well, especially since I have greylisting enabled on some email addresses, so by the time the email login is delivered, the login session has already timed out and of course the sender uses different mail servers everytime. So in some cases, it's nearly impossible to login and takes minutes...

Re: cURL removes bug bounties

#49
post #18

An entry fee that is reimbursed if the bug turns out to matter would stop this, real quick. Then again, I once submitted a bug report to my bank, because the login method could be switched from password+pin to pin only, when not logged in, and they closed it as "works as intended", because they had decided that an optional password was more convenient than a required password. (And that's not even getting into the di…

> An entry fee that is reimbursed if the bug turns out to matter would stop this, real quick. The problem is that bug bounty slop works . A lot of companies with second-tier bug bounties outsource triage to contractors (there's an entire industry built around that). If a report looks plausible, the contractor files a bug. The engineers who receive the report are often not qualified to debate exploitability, so they j…

I don’t think it works for curl though. You would guess that sloperators would figure out that their reports aren’t going through with curl specifically (because, well, people are actually looking into them and can call bullshit), and move on.

For some reason they either didn’t notice (e.g. there’s just too many people trying to get in on it), or did notice, but decided they don’t care. Deposit should help here: companies probably will not do it, so when you see a project requires a deposit, you’ll probably stop and think about it.

Re: cURL removes bug bounties

#50
post #2

A list of the slop if anyone is interested: https://gist.github.com/bagder/07f7581f6e3d78ef37dfbfc81fd1d...

All of those reports are clearly AI and it's weird seeing the staff not recognizing it as AI and being serious.

I thought the same, except I realised some of the reports were submitted back in 2023 before AI slop exploded.
Post reply on HN