It's gotten easier finding vulnerabilities, so every day without disclosure now brings a higher chance that blackhats find the bug. The deadline gets shorter accordingly.
Calling vulnerability research "extortion" is the kind of ridiculous, ignorant messenger-blaming the hacker culture has always made fun of.
What types of vulnerabilities does Project Zero find, in terms of their severity? And who are the companies that they are notifying?
You have to admit that there is likely a power imbalance here.
You directly called it "clearly a threat", and you indirectly called it plausibly extortion or else there would be no reason to ask if it's extortion.
But you need to explain on what general basis this even could be extortion.
And they're not "forcing the prioritization" of anything. They're just reporting bugs they found. They don't even need to warn the vendors at all if they don't want to.
Threats need an "or else". A non-negotiable publication is not a threat.
Nor do I consider it a threat when someone says "Items in the lost and found will be held for 30 days before they're donated to charity."
This is called "setting expectations" or maybe "communicating intentions".
Neither the users nor the vendors chose the 90/60/30 day limit.
Google is making an active choice in the design of their reporting process, and that is something that is open to critique and in some sense liability.
Why is Google choosing to report unlimited number of bugs, but a different Google program will only pay to fix 3 bugs? (https://bughunters.google.com/about/rules/open-source/patch-...) Why are not all Project Zero bugs exempt from that limit and awarded a minimum reward?
These are legitimate questions to ask.
if anything liability is on vendors that claim to be secure but actually aren't.
and sounds like you want a free money printer: write bugs, report to p0, get money to fix it.
So it is absolutely possible that nobody would ever find a memory corruption bug in a Lucas Arts SCUMM VM video transcoder if Project Zero didn't go poking around.
But because they did, and chose NOT to fund the fix, they DO carry some fault for anyone who acts on the bug after they disclosed it. Or if it is fixed in time, they must accept responsibility for consuming resources of a project they use but did not contribute to.
And the free money printer argument is absurd. The projects that Google uses are notable enough that writing bugs on purpose would be self-defeating. A project that write bugs on purpose would simply lose all users and nobody would care anymore.
Did they ask Google to decide how quickly they need to fix reported vulnerabilities?
Same free will Google uses to decide to spam them with reports, they could use to exempt those fixes from the 3 per month limit in Google’s already existing vulnerability fix reward program.
They don’t _have to_. But then I am free to call them out on it.
https://bughunters.google.com/about/rules/open-source/patch-...
Do projects ask hackers to hack them?
> Did they ask Google to decide how quickly they need to fix reported vulnerabilities?
It is irrelevant and this is the point you don't get: Google is not forcing anyone to do anything. They just say "I found this problem in your software, I am notifying you and in 30 days from now the whole world will know. Do what you wish with this information."
> They don’t _have to_. But then I am free to call them out on it.
It is the internet, do whatever makes you sleep better at night.
What is the purpose of the message that Google sends if not to pressure the project to fix the issue? And why is Google doing this at all if not to pressure specific behavior?
I think Googke is doing the world a big service publishing vulnerabilities as soon as they are found. It would be even better if they publish working exploits too.
Well, vendors can be more invested in building secure software and users get a lesson in why the "Check for updates" button exists in many devices' configuration options.
Google is not liable in any way for the vulnerabilities it finds.
What happens if a project has a vulnerability disclosure policy with a mandatory 90 day period, and Google ignores it starting 1.1.2027 and releases after 60 days?
You might wish that, but in the US at least they literally are not. There is no "security bugs" exception to the First Amendment. Anyone who finds one is perfectly free to shout it to the world instantly, or never, or anything in between. There is no gray area or complexity here as a matter of law. As a matter of morals, it is quite complex, and only getting more so in the age of LLMs. It was always the case that knowing a bug existed will let operators do "something" whether there is a patch or not, even if that something is "shut off all network access until patched", and it was always the case that anything one party can discover somebody else could at any moment, or at any earlier point from release before the second discoverer. LLMs can tremendously accelerate the discovery angle and expand the parties likely to do it, and might also speed up patching even by users of the software vs the devs.
>What happens if a project has a vulnerability disclosure policy with a mandatory 90 day period, and Google ignores it starting 1.1.2027 and releases after 60 days?
They can apply any social or economic pressure they're able to, otherwise too bad for the project? They can set whatever policy they want, nobody else is under any obligation to follow it unless contractually obligated.
It’s not the vulnerability that is the problem, it’s the timeline.
That’s what the original article is about. The 90-60-30 limit is something Google actually chooses, and that is not a first amendment issue.
Imagine a research found a vulnerability in Google and said, “You have 90 days to transfer 1 000 000 to my account or I will make the vulnerability public”. Pretty sure that would be considered actual blackmail and would be illegal.
It’s kind of tricky to see where the line would be. Google is effectively saying “You have 90 days to fix this vulnerability, in the software we use to make billions, or we will make the vulnerability public”. It’s not a huge difference. At best, you could argue it’s two different departments: one that find vulnerabilities and the other that makes money from the project.
Wonder no more. They have zero liability either way.
>That’s what the original article is about. The 90-60-30 limit is something Google actually chooses, and that is not a first amendment issue.
Uh. Choosing time/place for speech is absolutely a 1A issue. Google (and you, me, and anyone else) is completely protected from legal action in how and when they make a unilateral decision to speak using their own resources.
>Imagine a research found a vulnerability in Google and said, “You have 90 days to transfer 1 000 000 to my account or I will make the vulnerability public”.
Yes, as you say that'd be blackmail but that's completely irrelevant to anything you have said or anything in this case. Google is not demanding money.
>It’s kind of tricky to see where the line would be.
No. It's not actually. Blackmail is extremely well defined in law and caselaw. No demand for anything? No blackmail.
>“You have 90 days to fix this vulnerability, in the software we use to make billions, or we will make the vulnerability public”. It’s not a huge difference.
Yes, it's a huge difference, even if you were being honest in your statement, which you aren't. Google doesn't have any "or we", they just say "when we find something, we've decided we'll generally try to let you know, and then at X time later we'll disclose it no matter what you do or don't do, so that then other mitigations can happen, unless we feel like doing differently." Which is 100% fine. Somebody can fix the vulnerability they introduced themselves, or not. Or they can try to get someone else to do it (depending on the project and whether Google cares, it might well be a Google engineer or LLM who offers a patch). Once it's out there, everyone else who uses said software can also try to patch or otherwise ameliorate it or move to something else, based on their own considerations, or not. That's just... normal society and market of ideas? And it doesn't make any difference is whether Google makes billions or zero dollars.
And if something is just a personal / hobby project that you don't want to support - that's also fine. Having the security vulnerability published just means people using it have a more realistic view of the situation.
What do you think Google is extorting from the publishers of insecure software - reduced security vulnerabilities? Or what is it that you think Google is actually after by doing this?
> guise of security
What do you think is the real motivation if not security?
As seen by the infamous FFMPEG incident: https://thenewstack.io/ffmpeg-to-google-fund-us-or-stop-send...
In fact, the article cites one of the FFMPEG maintainers as being grateful for the vulnerability reports.
Did I miss something?
Google is extorting benefit, specifically fixes to software it heavily depends on for its multi billion dollar business, by coercion, specifically by actively threatening the project with reputational damage in 90 days if certain action is not taken, even if the action is not in the vendors best interest.
As a thought experiment, imagine if Google was reporting this to the project, but _without_ the 90 day limit. The one that the original article describes going down to 60 then 30 days. Yes, you might first think "that will cause the projects to never fix bugs" which might be true for some projects, but you do realize how legally that would completely change the dynamic between Google and the project and remove the entire extortion part from the picture? Or indeed, if they simply published it without any notice at all.
Whether or not other people also happen to benefit is related, but it doesn't remove the fact that Google also benefits.
Or if you would like a more vivid picture:
If the Mob forces you to give them a room in your hotel for illegal poker tournaments and then gives you tips on how to make the windows safer so that bricks can't fly through them, it does improve safety for all your clients but it's still extortion.
I would prefer ffmpeg team to have the time to focus on slightly newer stuff, as a user myself.
Just because the response can be "No", it doesn't mean Google didn't require _something_ from ffmpeg.
If they wanted to, they could also have "close to bug when fixed and we will only then notify the public", or they could have 0-day and just publish without notice.
But because they _actively choose_ 90 (60, 30) day windows, they _do_ require something from the projects that they report on.
It requires zero things from ffmpeg. As it is today, they privately contact them with info about the vulnerability and also informs them that in 90 days the whole world will know about the vulnerability too.
ffmpeg ca either fix it if it wants or be "cool story bro, yolo".
Why would a project get to tell somebody who found a vuln when they can talk about it to the public?
Imagine you go to a restaurant and see an issue with the food. You tell the restaurant “hey I’m writing a review of this. I’m going to publish it in a month; if you want to include any response before that time I’ll include it in my review”.
It would be nuts for the restaurant to say “actually we require you wait 180 days to publish”.
You can also take a look at how essentially all investigative reporting works, where a reporter asks the subject for comment before publishing.
Famously, leaving reviews on TripAdvisor in Germany can get you sued.
I did some light searching here and the examples appear to match what I’d expect: you can be liable if you lie about facts, but if you’re sharing your opinions or accurately relating what happened, you’re fine.
Can you provide some examples for your claim?
Similarly, if there were a jurisdiction somewhere in the world where vulnerability research was criminalized I don't think that would be relevant to the conversation we're having here. AFAIK project zero is subject only to US law.
If they provided evidence of their claim, I would have learned something new and it would be potentially interesting to the discussion about the risks of making public factual disclosures in places other than the US. It’s not a matter of whether or not it would be something to celebrate.
Countries attempt, with varying levels of success, to regulate international entities based on activity they conduct elsewhere in the world all the time.
And as an aside, it’s not clear that Project Zero is actually purely US-based: https://www.google.com/about/careers/applications/jobs/resul...
For a lot of security people its collecting scout badges.
It all came to a head once before: https://thenewstack.io/ffmpeg-to-google-fund-us-or-stop-send...
And Google has a vested interest in FFMPEG, because it uses it heavily to transcode and process videos. So they absolutely benefit from the work, for free.
How is it extortion? Google does not create the vulnerabilities. It just validates them and makes the details public. It is a public service for everyone.