Open source project curl is sick of users submitting “AI slop” vulnerabilities https://arstechni.ca/LAhpm #vulnerabilities #bugreports #hackerone #security #Tech #curl #AI

I mentioned the #hackerone AI slop thing on #LinkedIn

Why does the #AISlop problem exist at #hackerone (and likely other bug bounty platforms)?

Because apparently it works: https://hackerone.com/evilginx/hacktivity?type=user

It seems that some projects pay bounties for such AI Slop reports.

While I can't be 100% sure, we (#curl) count 8 "AI slop" #hackerone submissions so far, which also makes it roughly 8% of the submissions over the last year as we get around 100 submissions per year right now. It makes it roughly as common as we get legitimate security problems reported.

Round two in our fun game: "slop or not?"

(In here, the report is a rewrite of our previous published CVE in a way that I strongly suspect was done by an AI.)

https://hackerone.com/reports/2912277

Here's a link to today's AI slop #curl #hackerone report. Freshly disclosed: https://hackerone.com/reports/2887487

Marking them as spam now. #curl #hackerone (AI slop as "security vulnerability reports")

Also #hackerone: please STOP pushing your silly AI features to me. I don't care.

Did you know that #ONLYOFFICE has a bug bounty program on #HackerOne?

HackerOne is a cybersecurity platform designed to help companies in various industries find and eliminate vulnerabilities and bugs.

The ONLYOFFICE programme on HackerOne allows ethical hackers to report bugs and vulnerabilities and get rewarded.

More information: https://www.onlyoffice.com/blog/2023/08/onlyoffice-hackerone-program-summer-23-updates

#Discord told me on #HackerOne that this isn't a security #vulnerability, so cool, I'll talk about it publicly.

You can disable 2FA¹ on another person's account if you get access to their phone momentarily.

All you have to do is create a new account and put their phone number in as the login; if you verify the code, it strips it from the other account with no warning, and they can't take it back.

So have fun I guess?

¹ SMS is not #2FA

Kolejny krytyczny błąd załatany w GitLabie

Po dwóch miesiącach od poprzednich problemów, które opisywaliśmy, GitLab wydał kolejne poprawione wersje, zarówno Community Edition, jak i Enterprise Edition, oznaczone numerami 17.3.2, 17.2.5 oraz 17.1.7. Podobnie jak poprzednio, najpoważniejszy błąd, oznaczony symbolem CVE-2024-6678, pozwala – w pewnych okolicznościach, które nie zostały sprecyzowane w ogłoszeniu na stronie GitLab – na zdalne wykonanie...

#WBiegu #Cve #Gitlab #Hackerone #Podatności #Websec

https://sekurak.pl/kolejny-krytyczny-blad-zalatany-w-gitlabie/

The original #hackerone report for #curl's CVE-2024-7264: ASN.1 date parser overread is now published:

https://hackerone.com/reports/2629968

Just a reminder: with those bug bounty platforms like Bugcrowd, HackerOne or whatever, as a security researcher you are not their customer, you are the product.

If there is a conflict they will tend to side with their customer, meaning the company running the bug bounty program. Good luck proving that you have a right to disclose that vulnerability. They will pressure you into not disclosing as long as the company is opposed. So if you still want to decide anything it’s better not to grow too attached to that account because it will be used as leverage against you.

And they will try very hard to filter reports before these reach the company. If your report is more difficult to understand than the typical report for this program – good luck reaching the company, you’ll need it. It’s very likely that your report will be closed as “out of scope” with all appeals falling on deaf ears. The bug bounty platforms are paid for filtering, not for letting reports through just because they have doubts about them. You might need to think about other ways to reach the people actually in charge.

it has been nearly three months since the last valid #hackerone report against #curl

Just saying.

I bet you can't find anything to report.

#curl project is so effective in resolving reports they've broken #Hackerone https://hackerone.com/curl/policy_scopes

The #HackerOne saga continues: Now the analyst fails to understand how overwriting arbitrary root owned files is a privilege escalation to root.

I think I might need to request Mediation.