Disclosure to the company is only half of responsible disclosure.
- Report bug to company privately, and specify a date where the details will be made public. 90 days is a good starting point, but there is room for negotiation up or down depending on how complex the bug is (more complex = harder for someone else to discover = less urgency to patch) and how much impact there is (more impact = more risk if someone malicious discovers it = more urgency)
- While you wait, apply for a CVE number and determine a CVSS score - this helps signal how critical the bug is
- Once the company publishes a patch (or the embargo date is reached, which ever comes first), publish details of the research
The point of responsible disclosure is to balance the vendors need to have time to fix security bugs before the details are publicly known against the customers right to know that there are unpatched bugs so they can take measures to mitigate their risks. It isn't a free pass for vendors to never patch things
Not so in Germany, where you can be hit with charges by the company. In one famous case in 2021, the conservative party pressed charges against a data researcher, after she responsibly disclosed a massive data leak via their party app. After the court determined, that afromentioned data was insufficiently secured, those charges were dropped.
This proved to the tech-side in Germany, that responsible disclosure just harms yourself in the end and that German companies (and political parties) might as well go fuck themselves.
Edit: Grammar
Man germany at the highest clown rating in the digital era.
Somewhere in the HQ of the german conservative party
Disclosed responsibly
Received a Cease & Desist order with threat of litigation if released to the public
¯\_(ツ)_/¯No good deed goes unpunished
Sure would be a shame if it was leaked anonymously online...
Unfortunately this is a product not many care for nor know about, and I had a personal working relationship with this vendor, so even if it were “leaked anonymously” they could point back at me and make things a living hell.
At this point it’s been almost five years. They made their stance known. The exploit isn’t one that can be done completely remote without some internal knowledge to the setup of the equipment. It’s old news and they’re better off fading away in obscurity. I just won’t bother to try helping them make their products better and more secure.
It's very responsible of you to be thinking of the poor corporation; they needed a hand from a hardworking volunteer like yourself and you did the responsible thing and made their lives easier. Hurray!
Release the vulnerability to the dark net.
Don't release it to the public. Release it to a trusted professional with an obligation to release it to the public. "Oh no I don't have the data anymore. I gave it to X to see if they'd have better luck! convincing you!"
Mostly though, going to every possible channel and reporting publicly as a last resort is HEAVILY unlikely to result in legal action. Traditionally, I mean. Fuck if I know nowadays.
we acknowledge this is a zero day threat and is being actively exploited but we don't see the need to release an out of bad patch.
This exploit will be resolved on our next patch ETA next month.Looking at you non specific firewall vendor.
At least you're reporting legit vulnerabilities. Meanwhile I'm over here swarmed by "vulnerability reports" about SPF for a fukken subdomain that never gets used for email, and has it configured correctly already 😑
You should look up Beg Bounties by the guy that does haveibeenpwned
Edit: here it is for others to see
I've not heard of it, I'll check it out!
I have reported a few vulnerabilities in the last years, but sometimes it is hard to judge whether or not it is a real vulnerability or just a minor bug.
But I'd rather report one bug too much than keep silent about it.
Then people wonder why it just gets leaked online.
