Please report bugs. If you - or someone else - improves exploitability after initial report, the bounty will be increased. If you're second reporter, you will be pro-rated.
I guess I can only speak for our bounty program but come on industry, you can do better.
#bugbountytips
Do not report open redirects without fully analyzing and seeing potentials of it. Thanks to random guy who reported open redirect, our report for full SSRF leaking client secret of integration claimed dupe.
Again: do not report open redirects #bugbountytips
Reminder that our bug bounty program accepts PoCs (e.g. , verifiable in an address sanitizer builds that you can find here https://t.co/ovY7HAM43k).
No need to write a full exploit.
More here https://t.co/lTEoqzuQ4U :)
@pwning_me Sorry to hear it did not work out. Let's meet at the conference, we're happy to accept a non-working exploit in the bug bounty program even if it's just a poc. :)
I was hoping to compete in Pwn2Own with a Firefox full-chain entry, but unfortunately it was rejected. I’ve reported the vulnerability to the Mozilla team.
@qriousec There was a Firefox 150.0.1 update last week and a Firefox 150.0.2 update just today. Make sure that it still works and we're looking forward to meeting you next week :)
When we said that we found and fixed hundreds of bugs in Firefox using AI, people were skeptical and said: Where are the bugs?
Well, here they are. We are unhiding 12 security bugs that are representative of the issues we have found.
https://t.co/aIZ8p1Wxso
@LiveOverflow The bug info is public, including test case and patches. If you want to follow along, look at bug https://t.co/dNi1tgydQQ (Day 1 exploit) and https://t.co/C7KUB09xcb (Day 2)
See @LiveOverflow's documentary on Firefox and pwn2own and learn what it was like to fix not just one but TWO Firefox security bugs at rapid time. https://t.co/ipH9EMBTSf