Project Zero will disclose vulnerabilities 90 days after reporting

(projectzero.google)

307 points | by hacb 1 day ago

13 comments

  • Aissen 17 hours ago
    I wonder how this will work with Android's current long delays between patching (and distribution to trusted vendors) and public disclosure.
    • kps 9 hours ago
      Note that Google doesn't get special treatment from Project Zero. There are (as of this comment) four Google issues disclosed after missing the deadline.

      https://project-zero.issues.chromium.org/issues?q=status:ope...

    • fc417fc802 16 hours ago
      Presumably it will force that entire chain to become much faster than it currently is. Which would be an unequivocally good thing IMO.
      • sigmoid10 15 hours ago
        The first party and flagship security patch chain was always fast. The real issue is the bottom-of-the-barrel third party budget sector chain. They already need 6+ months (if they patch at all) despite 90 days disclosures having been industry standard for a while. Tightening these timelines won't make them care, it will only increase threat levels for low-income users.
        • carlmr 7 hours ago
          >The real issue is the bottom-of-the-barrel third party budget sector chain

          The real issue is that it's even possible for companies to make custom Android ROMs that don't get the newest security patches.

          Any company that doesn't have the security patch should not be allowed to keep distributing a non-stock version of Android.

          • fc417fc802 5 hours ago
            I'm okay with companies selling one off devices that they don't intend to maintain but I think they should be legally required to disclose that fact up front and in such cases to provide the user with the means to upgrade things himself.
            • carlmr 2 hours ago
              Phones are too central to people's lives, we need to make sure that companies don't just sell you bloated Android without security patches.

              If they want to sell bloated Android, at least they have to be held to the same standard as stock Android.

              If they can't keep up with patches we should levy hefty fines that make it financially unattractive.

              • fc417fc802 36 minutes ago
                Where's the harm if the device carries a clear disclaimer and you the owner are provided with the relevant source code and the means to unlock the bootloader? We shouldn't criminalize open devices or prepackaged software. The problem IMO is caused entirely by vendors providing a vulnerable product, locking it down, and a nontechnical end user lacking the means to discern any of this up front.
        • fc417fc802 14 hours ago
          I hate to say this, but that's a good thing IMO. It will serve to either force those companies to finally start caring to fix their process or it will force the relevant users to get hacked until they vote with their wallets or (less likely) possibly force bootloaders to be unlocked or perhaps governments to finally step in and mandate some minimum level of software maintenance.

          The tools enabling these exploits exist and aren't going away so burying our collective heads in the sand by allowing messes to be swept under rugs isn't a productive response.

          • tomsmeding 11 hours ago
            > It will serve to either force those companies to finally start caring to fix their process

            Those companies care about their revenue; they care only about the security of their customers' devices if it impacts their business success.

            > or it will force the relevant users to get hacked

            That it well might.

            > ... until they vote with their wallets

            They won't, because the next company over is just as bad, and the first-party devices are too expensive. And anyway the knowledge of which companies patch early may not even spread outside the tech circle.

            > ... or (less likely) possibly force bootloaders to be unlocked

            By whom? I have no idea what party would arrange that.

            > ... or perhaps governments to finally step in and mandate some minimum level of software maintenance.

            Now that would be nice, but that would be regulating the industry, and since when is that happening?

            I doubt this is a good thing.

          • scott_w 10 hours ago
            >> it will only increase threat levels for low-income users.

            > it will force the relevant users to get hacked until they vote with their wallets

            By definition, a low-income user has very little "wallet" to vote with. Government stepping in is really the only workable solution.

          • Aissen 13 hours ago
            > perhaps governments to finally step in and mandate some minimum level of software maintenance.

            EU's CRA is coming (already delayed).

            But it will all depends on enforcement strength. Until the first supermarket (or online reseller) is heavily fined for selling a smartphone that no longer receives updates, I won't hold my breath.

          • cowlevel 13 hours ago
            FWIW right to repair is already in force in the EU, which you'd think would require bootloaders to be unlocked, but they probably won't be until someone sues them over it.
  • my-huge-pony 1 day ago
    Starting today, our policy is “Full 90”, i.e. vulnerabilities will be disclosed 90 days after they are reported to the vendor.

    On February 2, 2027, we will move to a “Full 60” policy where vulnerabilities are disclosed after 60 days.

    On January 3, 2028, we will move to a “Full 30” policy where vulnerabilities are disclosed after 30 days.

    • Wowfunhappy 23 hours ago
      WTF with a 30 days deadline in 2028?

      I thought they made a strong case for removing the additional 30 day patch rollout time. But reducing the entire process to 30 days total seems needlessly harsh and I didn't think it was justified by the article at all. What if the bug is actually inherently hard to fix?

      • jgeralnik 17 hours ago
        After reading the first line of the comment I thought it was a criticism that 30 would be way too _long_ of a deadline in 2028

        With AI assisted vulnerability research the relative edge of project zero is going down - anything they can find can likely be found by others in a similar timeframe. We see this today with the parallel discovery of php2shell by many groups in the same few weeks

      • Gigachad 21 hours ago
        If the bug can’t be fixed in 30 days, the service should be disconnected from the internet until it can be fixed.
        • jsiepkes 13 hours ago
          Google isn't doing this because they think this is best for all of this. They are doing it because it is best for Google. This is like when companies say they hate regulation, except for when they can weaponize it to bully (smaller) competition.
        • cookiengineer 19 hours ago
          That is not how scale works.

          Some (likely most) projects have just non-paid people working on it in their free time. That's the reality of open source.

          • Gigachad 18 hours ago
            You should not connect a service maintained by individuals in their free time to the public internet. Put it behind a VPN or local network only and then you don’t have to worry.

            Delaying disclosures is a false sense of security when the attackers are running the same scans Google is. They will have exploits faster than 30 days.

            • perching_aix 9 hours ago
              > Put it behind a VPN or local network only and then you don’t have to worry.

              This is not how software works whatsoever, to the extent that I have to wonder what relevant expertise do you have in the area. Like this is for all intents and purposes just nonsensical.

            • sam345 18 hours ago
              This is the kind of thinking that in the 90s would have kept the internet exclusive to the domains of university and government. Every new technology has risks and people adapt. In the early part of the 20th century we might as well have kept cars away from private citizens and relegated transportation to buses, trains and professional drivers. Need private transportation? Use a horse. What with the number of people killed and maimed every year it's just not worth it. Take away our keys and mandate public transportation please.
              • Gigachad 18 hours ago
                People will adapt by updating stuff faster than 30 days, and by everything that doesn’t do that getting hacked.
                • aunderscored 15 hours ago
                  No. People will stop caring because they do not wish to have the extra stress of this. Which kills open source and therefore a lot of collaboration and innovation. Not to mention killing the open internet.
                  • dns_snek 9 hours ago
                    That's like blaming the city for killing your golf course with [necessary] water rationing mandates.
            • billstickers 14 hours ago
              [dead]
          • fc417fc802 16 hours ago
            I see only two possibilities. If it's a proprietary product that should either be rapidly fixed by the vendor or abandoned by the customer. Alternatively, if it's a FOSS project then if the maintainers are unresponsive the end user can simply request his LLM of choice to patch it for him. I honestly see no issue here. It isn't how things used to work even as recently as a year ago but it seems to be the only sensible way they can work going forward.
          • bawolff 18 hours ago
            Well if an attacker starts attacking things in the wild, you better find a way to address it in faster than 30 days.
            • margalabargala 18 hours ago
              That would be the problem of the people running the software, not writing it.

              Considering the direction software and their exploits are going with AI, if 30 days is insufficient in 2028 then that's useful signal to the people running that they should move elsewhere.

              • cowlevel 17 hours ago
                Still is their problem either way. Who else's would it be?
              • pjmlp 17 hours ago
                Only until cybersecurity liability legislation finally starts to kick in, then those writing it will have a solid reason to assign the necessary resources to make it happen.
                • xoa 12 hours ago
                  >Only until cybersecurity liability legislation finally starts to kick in

                  In America software is protected by the First Amendment, so most software (and all open source for sure) cannot be subjected to "cybersecurity liability" of the sort you seem to be envisioning. Congress could have an angle when it comes to stuff that is sold, including in particular hardware and subscription services though there will be both plenty of lobbying and plenty of potential landmines involved in any such effort.

                  But with anything free there is no commercial angle involved, no contract. It's just speech that's put out there, identical to the posts we're writing here on HN right now. Software bugs aren't true threats, incitement, defamation, or obscene.

                  Other countries of course could take a different tack, but they'd then face "OSS becomes fully American" and I'm deeply skeptical that'd work politically.

                  • pjmlp 11 hours ago
                    There is this thing called soverignity where goveremnts can legally track down the citzens who fails to comply, and whose actions can endager the country in whatever means the forces in power decide it may be.

                    Also when US gets a saner goverment back, I am quite sure CISA will have yet another opinion on the matter, especially if national security is considered exposed in some media case.

                    • xoa 11 hours ago
                      >There is this thing called soverignity where goveremnts can legally track down the citzens who fails to comply, and whose actions can endager the country in whatever means the forces in power decide it may be.

                      Perhaps in your authoritarian fever-dreams or whatever shithole country you current reside in, but no in the US.

                      >Also when US gets a saner goverment back, I am quite sure CISA will have yet another opinion on the matter, especially if national security is considered exposed in some media case.

                      And I'm quite sure you're full of shit.

                • fc417fc802 16 hours ago
                  Any sensible legislation will unconditionally exempt the authors of FOSS software. If that is ever not the case the logical consequence is all FOSS contributors moving to pseudnonymous identities and collaborating exclusively via tor.
                  • dns_snek 10 hours ago
                    For example see the EU cyber resilience act (regulation 2024/2847). It sets out nuanced rules regarding FOSS.

                    If you simply run or contribute to a FOSS project then you don't have any obligations, those kick in when you distribute software for profit and your obligations scale with the size of your business. Companies that fail to promptly address security vulnerabilities will face strict liability for damages.

                  • pjmlp 15 hours ago
                    Or we go back to shareware and 30 days demos, most likely.
          • Onavo 17 hours ago
            Then Google can just send a patch. What better marketing than that if you want to sell people on your periodic table AI.
          • perching_aix 18 hours ago
            great! so companies and individuals will get to learn this reality of open source.

            a reality that has always been blatantly obvious, unless one only listened to its all too many zealots.

        • baq 12 hours ago
          They should submit patches and/or publish fixed forks. Fighting irresponsibility with more irresponsibility is plain dumb.
        • kapilvt 19 hours ago
          lol, and if its in a widespread library in an embedded device? Thanks for compromising the internet, aka there is a tension inherent, not that i disagree with policy and the forcing function underneath, but it is quite a different perspective for non corporate projects.
          • Gigachad 19 hours ago
            If you have an embedded device connected to the Internet that doesn’t get updates and has vulnerabilities that can be picked up by LLMs then you need to unplug it.

            That is the world we live in now and pretending otherwise is reckless and leads to mass hacking like the recent supermarket fridge hacking.

            Only devices and applications that can respond to security reports quickly should be connected to the internet.

            • Symbiote 13 hours ago
              (Now the fridges could be updated, and some supermarkets announced that they'd updated some, most of all of their fridges, either before the hacking, or after the first incident.)
            • SR2Z 19 hours ago
              I (somewhat) agree.

              Lots and lots of devices are gonna get turned into botnets and tons of personal information is going to get leaked. However both of those things are already true.

              Constant attacks mean the future will hopefully see local-first devices that don't need software at all.

              Want to put them on the internet? They go behind gateways which are better maintained, because a world where every teenager can hack a vending machine through its vestigial Bluetooth stack would finally need to be secure to function.

          • akerl_ 12 hours ago
            Project Zero isn’t creating these vulnerabilities, and there’s no reason to assume they’re the only ones who have found them.
          • lalaithion 19 hours ago
            if there’s a vulnerability in a widespread library in an embedded device that can’t be patched, people should go smash the device with hammers.
            • quaffcode 19 hours ago
              They actually should, those devices get hijacked for botnets.
            • sam345 18 hours ago
              This is ridiculous. Vulnerabilities dont mean severity of damage and risk assessment is better made by individuals themselves. If you're afraid of botnets get a firewall. But go ahead and mandate this. Let's do it. Better yet, let's require the registeration of all unable to be patched devices and give the government the right to smash those devices if they don't get updates. That's the world I want to live in.
              • fc417fc802 16 hours ago
                Or, crazy idea, we could all just do what google is saying they will do here and the situation will naturally resolve itself.
      • fn-mote 23 hours ago
        They expect that in another year LLM-assisted fixing will be the norm. It probably is already.

        The article says they are willing to negotiate in exceptional cases, and mentions Spectre.

        • sippingabonedry 22 hours ago
          It's not the fixing that's usually the problem, it's more the testing.

          The testing can take a while, assuming it's a consideration at all.

          Skipping testing is how you end up with another Crowdstrike scenario.

          • tybit 21 hours ago
            Crowdstrike was a good example of why you should never allow global updates to roll out all at once , even for configuration changes. Cloudflare has learnt the same lesson recently https://blog.cloudflare.com/18-november-2025-outage/

            Bug fix speed isn’t particularly relevant, rollout speed is.

            • asdfasgasdgasdg 20 hours ago
              Two week rollouts should be (and needs to be) sufficient in any product that imposes security risks. Attackers will not wait longer.
              • SR2Z 19 hours ago
                Two week rollouts are insane. Three days, in the vast majority of contexts, is generous.

                I hate to see slow rollouts. The single best thing you can do for fighting bugs is to roll out with canaries; weekslong rollouts only make sense when someone actually has to be in the middle of a cursed release while it runs.

                If there's a bug in your code and it's rare there isn't much disruption. If it's not rare, why didn't your tests catch it?

                • fc417fc802 15 hours ago
                  > If it's not rare, why didn't your tests catch it?

                  Who can say? But it happens. If it didn't then deploying straight to production wouldn't be a problem.

          • ikiris 18 hours ago
            You're both missing the point. The actual issue is llm exploit generation. If they can find it, so can other bad actors. We can't sit on issues anymore the time to exploit is now tiny or negative in some cases.
      • doodlesdev 23 hours ago

           > What if the bug is actually inherently hard to fix?
        
        Then users might just as well know about it so they can avoid the software while it's vulnerable.
        • Wowfunhappy 20 hours ago
          Every piece of software you have ever used almost certainly has critical security vulnerabilities, right now, no matter how up to date it is. However, you don't know about them and neither does anyone else.
          • akerl_ 12 hours ago
            > neither does anyone else

            What makes you think this is true?

          • dullcrisp 20 hours ago
            If you can prove that no one else knows about them then I see no problem.
            • Wowfunhappy 19 hours ago
              Obviously you can't prove that, but again, you can't prove that for literally any software you're using right now.

              Let's say a bug hasn't been found for the past 20 years. Google finds it, but it's going to take longer than 30 days to fix. Is it really better to let everyone know about it after 30 days? If no one else has found it (true, as far as we know) in the past 20 years, what are the probabilities it will be found by a second person in the next few months?

              • fc417fc802 15 hours ago
                > Google finds it, but it's going to take longer than 30 days to fix. Is it really better to let everyone know about it after 30 days?

                Yes it absolutely is. Because going forward google will almost certainly have found it using the same widely accessible tool - LLMs - that everyone else also has access to. The fact that a bug has gone unnoticed for the past 20 years has no bearing whatsoever on the future year (or probably even six months). At this point given that team A has found a bug the probability that teams B thru Z will also find it within the next half year or so is extremely high.

      • tomkarho 7 hours ago
        I think it was ffmpeg developer who pointed out the inherent problem with this: quantity. 30 days to fix one vuln seems like reasonable when you are a billion dollar corp with thousands of pairs of hands and another thousand AI agents to throw at the problem but when you are that one developer from Nebraska thanklessly maintaining critical infrastructure (for free) it's not a matter of if but when will that burnout hits and your critical software is now a fart in the wind up for grabs for anyone willing to take up the charge.
        • marshray 6 hours ago
          They should have thought about the before representing their bug-ridden code as suitable for critical infrastructure.

          I know this sounds harsh but it really would be better for the world if these "processing complex untrusted data structures in C" enthusiasts found another hobby.

          • 29083011397778 4 hours ago
            > They should have thought about the before representing their bug-ridden code as suitable for critical infrastructure

            Typically it's presented as-is and without any form of warranty, but in the hope it will be useful - not "suitable for critical infrastructure".

            Perhaps those using it for "critical infrastructure" can write their own utilities, or chip in to support the developer whose hard work they apparently rely so heavily on, so bug fixes aren't done merely in the dev's unpaid time-off?

            • marshray 3 hours ago
              "Critical infrastructure" wasn't my phrase and I agree that the corporations who are using open source have a moral and pragmatic obligation to fund its maintenance.

              But what does a developer (open source or not) who releases a container format parser and codec collection upon the world expect people to do with it if not run it on malicious data on personal devices?

              • 29083011397778 1 hour ago
                > But what does a developer who releases [...] upon the world expect people to do with it

                Sometimes you build things to explore how they work, or to test your assumptions about how something would work. To build your own knowledge about a format, language, or system. Hell, sometimes it's just the middle of a venn diagram between fun and practice.

                And, because it's easy to throw something up on GitHub, you can say "Look at this cool thing I made", "Look, I actually can do what I claim on my resume", or "Anyone struggling in the same place as me can use this as an example workaround, or inspiration for a solution"

                Nobody has to, or is even necessarily expected, to use it. Sometimes it's just the author sharing this cool thing they made.

      • dns_snek 11 hours ago
        Users should be made aware that the product is vulnerable and to take appropriate precautions. 30 days always should've been the norm.
      • cowlevel 17 hours ago
        If AI can find it in 30 days, so can the attacker's AI. Continuing an embargo of something the attacker already knows is counterproductive.
      • perching_aix 22 hours ago
        i find it more surprising they put it so far away really.
    • a34729t 3 hours ago
      Next year there has been a discussion of Advent of Zero Days. So hold on to your butts.
    • cookiengineer 19 hours ago
      Oh the irony here.

      AOSP still has a 6 months holding back patches delay, the reasoning was "improved security".

      So, what is improving security now? Fast patches or slow patches? :)

      • cowlevel 17 hours ago
        You misunderstand - denying patches to downstream vendors improves financial security for Google.

        But they actually did this to comply with the EU Cyber Resilience Act. When a patch is released, a legal clock starts ticking - anyone who doesn't apply it promptly is liable for any resulting damages.

    • ares623 1 day ago
      Perhaps eventually, they can finally live up to their namesake. On January 1 2029, we will move to a "Full 0" policy where vulnerabilities are disclosed after (looks at camera) zero days.
      • InsidiousWombat 1 day ago
        IMO the disclosure should ~day-two after there is a fix/workaround available

        Releasing before that is non-actionable by many actors (aside from taking the service completely down I guess). Any time after fix is available is just allowing vulnerable systems to be attacked and is playing favourites with who gets fix and who doesn't

        • aurareturn 18 hours ago
          Nah. You need a clear deadline or people will just drag it out.
        • habitue 23 hours ago
          So you're saying:

          2 days after there's a fix, with a max of 90 days after disclosure?

          Because you still need to have the 90 days no matter what to induce the vendor to create a fix. Otherwise (many) just sit on it forever.

          • fn-mote 23 hours ago
            > you still need to have the 90 days no matter what to induce the vendor to create a fix

            You’re replying in a thread whose top level comment is that the 90 days will rapidly decrease to 30.

            Hope 30 is enough to induce them to fix.

            Maybe the future fixes will be “Reddit + Claude”, done at home.

      • esafak 1 day ago
        If AI is doing all the work I could see that; same day remediation.
        • nextaccountic 1 day ago
          Which means developers must trust AI blindly since there is no time to review the fix. Which also means that developers are completely unneeded
          • perching_aix 1 day ago
            No, that's not what it means. It just means that the benefit must outweigh the risk, as always. Making surgical patches to existing code is also quite different to introducing features, which is what developers typically spend their time on. Not that same-day patching would imply literally zero time to review either.
          • esafak 1 day ago
            That does not follow. Somebody stills needs to set it up. And maybe to sign off. The AI could instantly diagnose and summarize the problem and its remediation and you say the word.
            • jagged-chisel 1 day ago
              And someone who understands the whole thing needs time to validate that the remediation is indeed what it's supposed to be.
              • TeMPOraL 1 day ago
                No, they're not - they can just release and wait for another vulnerability disclosure. Then the loop between [Vendors] and Project Zero needs no humans in it.
                • jagged-chisel 23 hours ago
                  And that's how wallets and bank accounts get drained. Future's looking bright.
            • nextaccountic 22 hours ago
              The way you describe it puts the role of humans as merely decorarive and ceremonial. The work is done by AI and actually validated by AI too, and increasingly the role of the human is to give an ok to whatever the AI outputs
              • esafak 11 hours ago
                Today's it's to catch mistakes, but perhaps that won't be necessary either.
            • vorticalbox 1 day ago
              “Someone” being another AI agent.

              It’s agents all the way down.

        • newAccount2025 1 day ago
          AI is not doing all the work.
          • LoganDark 1 day ago
            Do we even know what AI will be doing in two years?
            • cowlevel 17 hours ago
              We can extrapolate from the last two years now that it's older than that. In 2024, although vibe coding hadn't been coined yet, AI was being used to autocomplete lines and functions with the tab key. Now it is autocompleting entire programs with a chat interface. In another two years it may be autocompleting whole projects with a neural interface.
            • jeltz 22 hours ago
              No, and neither does Google which makes their 30 days ridiculous.
              • Dylan16807 18 hours ago
                You can do a 30 day fix with just humans. It's not ridiculous.
        • ares623 1 day ago
          If AI is doing all the work then why would remediation be needed at all? Why can't the software AI produces be vuln-free if the same AI is used to detect them?
          • Gigachad 20 hours ago
            Because LLMs are not deterministic or predictable and make mistakes that they are capable of fixing.

            LLMs will write vulnerable code while the same model can find those vulnerabilities if you prompt it right. Some stats from a previous post was that the CVEs found in Linux were costing on average $1000 in api usage each. So having the LLM prevent writing vulnerabilities would explode the costs.

          • IncreasePosts 1 day ago
            Because the people finding the vulns aren't the people running the services.
            • thwarted 1 day ago
              Why aren't they? The people running the services can use the AI to find the vulnerabilities before they release.
              • Catloafdev 1 day ago
                You talk as though there is one AI model that is perfect and capable of identifying all potential flaws with no mistakes or omissions, and that access is free and unlimited.

                Reality is more complicated than that.

              • IncreasePosts 21 hours ago
                Project zero is run by Google, one of the few groups doing frontier models. If you consider their revenue streams, Google is the sole frontier player that can actually fund insane research and compute out of pocket without relying on any hype cycle.

                So, Google will have some model that is much more powerful than the publicly available models. Before releasing it to the world, they can use it to mitigate any issue it discovers anywhere

              • ares623 1 day ago
                Exactly. That's super irresponsible to knowingly release software that you haven't used AI to check if it had any vulns. There's zero (heh) excuse to release vulnerable software at that point.
                • canibalrex 1 day ago
                  Catching lots of bugs in software written with poor methodology is the new norm and that is not the same as releasing software that is not vulnerable. That is releasing software that needs increasing technological improvements or luck to find remaining vulnerabilities.
          • unsloppable 1 day ago
            Is the AI in the room with you right now?
            • TeMPOraL 1 day ago
              The Machine is everywhere. Watching us with ten thousand eyes. Listening with a million ears.
    • jordemort 22 hours ago
      they are altering the deal, pray that they do not alter it again
  • PeterStuer 8 hours ago
    Is this a hidden cloud/SaaS push? For bespoke on-prem systems even if you have a full software BoM and an active monitoring service, it is not like these systems have an auto-update functionality. And your timer starts running after the vendor of the sub-component or platform is finished.
  • wewewedxfgdf 1 day ago
    Ubuntu will need a LOT more time than that.
    • dannyw 1 day ago
      After seeing the latest vuln response times by Ubuntu, I switched my main PC to Debian; and will progressively migrate my homelab as I have time.

      Definitely much happier. There’s nothing I miss from Ubuntu.

      • Gigachad 21 hours ago
        Running trivy scans on my docker containers has really highlighted which projects keep up to date. I’ve been moving away from all the one person projects to more commercial offerings that keep on top of updates.

        Of course I don’t expect a single person to work every day for free, but I also can’t have a project with only a single dev exposed to the internet.

      • martijnvds 11 hours ago
        I switched back years ago, when they started promoting snaps.

        The principle (containerized apps) is fine, but the dependency on a single vendor's "storefront", is not.

      • InsidiousWombat 1 day ago
        Ubuntu is one thing (and is crazy it took so long) but RHEL somehow failed on that too.
    • jeroenhd 10 hours ago
      [dead]
  • glitchc 1 day ago
    It makes to hold out for disclosure if there's a pay day involved. Since this is Google, the bug bounty is not the issue. I say release right away. Nothing else will compel the company being reported on to fix otherwise.
  • level87 1 day ago
    Unrelated, but didn't realise .google was a TLD.
  • sylware 14 hours ago
    ... and gogol won't catch all vulns...
  • xcavier 14 hours ago
    90 days is literally a ‘hand written bankbook’ service standard. Crazy
  • Frost1x 1 day ago
    I’m not familiar with this specific effort but it seems like the companies digging around for the bugs should also offer similar access to their products that discovered the vulnerabilities to the vendors or OSS projects to patch them. Otherwise vendors might use this as a leveraged approach to get people to adopt LLMs, specifically theirs, so their products remain reasonably attractive. Google, OpenAI, Anthropic etc could just turn on existing software as a strategy to get more adoption of their tools.

    “Don’t like our constant stream of patches? For $10k/mo + tokens you can get access to the model to patch the vulnerabilities we disclose!”

    • Refreeze5224 1 day ago
      Project Zero has been around far longer than GenAI or LLMs, so your point is not really relevant here.
      • Frost1x 1 day ago
        How is it irrelevant? Just because an effort existed before some change, doesn’t mean it can be repurposed and leveraged for other purposes. It’s the entire reason law and policy for government isn’t set in stone and is adaptable, because culture, technology and so on change.

        The dynamic in this context absolutely has changed. Marginal cost to discover vulnerabilities from AI frontier labs and the big players has dropped significantly. The cost to patch is low, if you have access to certain resources. If you don’t, tough luck.

        So this argument is essentially against the entire argument of AI alignment guardrails right now. Maybe you disagree with those, but I for one am happy they’re doing some things to protect against bio related warfare engineering. This is a case of cyber that’s about grey. Even there the labs have limited access to some and are choosing winners.

    • sumeno 1 day ago
      The "product" that finds Project Zero bugs is the people who work for Project Zero.
    • darkamaul 1 day ago
      For sure I would love to get access to P0 researchers for a m 10k/months, but i don’t believe you can hire such talent for this sum.

      They are one of or maybe the most skilled security research team that’s doing public research and their blog is the source of many modern exploitation techniques

      For a while, asking your agent to act like a P0 researcher was a nice nudge to find better bugs !

    • ylk 1 day ago
      Usually you can’t find the kind of bugs P0 finds by just throwing AI at it. You need highly skilled people driving/guiding it. Highly skilled people are the bottleneck.

      In any case it’d be sensible to make yourself familiar with the “specific effort” before you make up your opinion on it.

    • Dylan16807 18 hours ago
      Your argument makes complete sense if the tools that find a bug can automatically make a patch, but a vendor getting a thorough bug report can't make a patch with anywhere near the same amount of ease.

      But that assumption is pretty crazy to me and your argument makes no sense to me.

    • InsidiousWombat 1 day ago
      That's kinda the problem with asinine "safety" idea the AI moguls have.

      It is just leaving people with less safe software. At least claude the limitations are actively preventing you from looking for security bugs in your own software

    • clhodapp 1 day ago
      You say that like it's a bad thing...

      I mean, sure, the cited $10k / mo is exploitative for small open-source projects but... in general, why wouldn't we want there to be pressure on companies and projects to use high-quality LLM-based checks if they want to see wide adoption?

  • massroot 15 hours ago
    This is unfortunately too slow. As their finances show & name states p0 they need to act accordingly 0 day patch & disclosure and with the advancement of Ai 0 hour, 0 minute 0 seconds needs to be on the near roadmap if they want to remain “p0” alphabet/Google/other big tech need to fund the patches if they intend to disclose and they need to do it much faster. 30 days time is laughable anyone with basic understanding of 0 days, Ai & latency knows this.
  • bmitc 21 hours ago
    Is this a version of extortion? Isn't this Google, a massive company with lots of power and control, forcing the prioritization of work on everyone under the guise of security? It's at least clearly a threat.
    • sethaurus 20 hours ago
      Project Zero doesn't create the vulnerabilities, it finds them. Vendors want unlimited time to fix their bugs. Users want to know ASAP if the software they are running is vulnerable. These things are obviously in tension, so you need a deadline.

      It's gotten easier finding vulnerabilities, so every day without disclosure now brings a higher chance that blackhats have already found the bug. The deadline gets shorter accordingly.

      Calling vulnerability research "extortion" is the kind of ignorant messenger-blaming the hacker culture has always ridiculed.

      • bmitc 20 hours ago
        I didn't call it anything. I asked the question to understand.

        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.

        • Dylan16807 18 hours ago
          > I didn't call it anything.

          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.

          • bmitc 16 hours ago
            Anything phrased as "You have <x> days to do something until we do <y>" is indeed a threat.
            • justin_oaks 16 hours ago
              Funny, I don't consider it a threat when my pharmacy says "You have 5 days to pick up your prescription until we reshelve the medication".

              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".

            • Dylan16807 16 hours ago
              You have two weeks until I celebrate Thanksgiving.

              Threats need an "or else". A non-negotiable publication is not a threat. It's someone sharing their schedule.

      • FabCH 17 hours ago
        You are ignoring the part of Project Zero that reports the vulnerability.

        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.

        • ExoticPearTree 13 hours ago
          > Neither the users nor the vendors chose the 90/60/30 day limit.

          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.

          • FabCH 13 hours ago
            Google is liable for their actions. In particular, Google is liable for choosing 90, 60 and 30 days waiting time.

            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?

            • xoa 12 hours ago
              >Google is liable for their actions

              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.

              • FabCH 11 hours ago
                See but I do wonder if it would be less liable for them to literally shout it out instantly.

                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.

                • akerl_ 11 hours ago
                  There’s a pretty big difference between saying “pay me hush money or I release this vulnerability” and saying “we found this vulnerability and we’re going to publicly disclose it in 30 days”.
                • xoa 11 hours ago
                  >See but I do wonder if it would be less liable for them to literally shout it out instantly.

                  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.

        • arccy 16 hours ago
          the bug exists regardless of p0. either p0 reports it and users can mitigate its impact or p0 doesn't report it and someone else finds it and users are exploited.

          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.

          • FabCH 16 hours ago
            Not necessarily. This view contains an inherent contradiction. If the bugs require skill to find, then Project Zero makes sense because it donates that skill. But if the bugs require skill to find, then "someone else finds it" stops being certain. Alternatively, if the bugs don't require skill to find, then Project Zero is not actually doing anything valuable.

            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.

            • ExoticPearTree 13 hours ago
              What are you blabbing about? Do you want Google now to fund the laziness of every software/firmware vendor on the planet?
              • FabCH 13 hours ago
                No, but how about they pay for project they use?
                • ExoticPearTree 12 hours ago
                  Are the projects they use requiring licenses for commercial use?
                  • FabCH 12 hours ago
                    Did the projects ask for vulnerability scanning from Google?

                    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.

                    • Valectar 11 hours ago
                      I think you're confused. Google isn't paying other people to fix bugs in their own software. Google pays people to find bugs in Google software so that they can fix it. The same service they are providing to other software projects, for free, they pay individuals for because finding bugs in Google software helps Google to improve it.
                    • ExoticPearTree 10 hours ago
                      > Did the projects ask for vulnerability scanning from Google?

                      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.

                      • FabCH 6 hours ago
                        That’s being disingenuous.

                        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?

    • kqgnkqgn 20 hours ago
      If you can't bother fix a critical security vulnerability in 30 days, you shouldn't be in the business of building software for others to use.
      • gib444 20 hours ago
        Those kind of comments read like: if you aren't Google (sized), you have no business building software
        • kqgnkqgn 19 hours ago
          Why does it take Google scale to address reported security vulnerabilities in a timely manner?

          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.

          • gib444 16 hours ago
            You know that colleague at work who goes around "helpfully" and constantly making suggestions about how you could improve your work and even criticising you in front of your boss?

            Yeah they're not doing it to help you but to sabotage you.

            But when challenged they profess they're just trying to be "helpful"

        • Dylan16807 18 hours ago
          Smaller companies have less code for bugs to hide in.
        • bmitc 19 hours ago
          This is sort of what I was getting at with my original post. I'm just curious as to the power dynamics here. Not everyone has $0.5 trillion in revenue every year.
    • no-name-here 18 hours ago
      > extortion

      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?

      • FabCH 17 hours ago
        Google is extorting free fixes for software Google depends on, instead of paying for them to be fixed.

        As seen by the infamous FFMPEG incident: https://thenewstack.io/ffmpeg-to-google-fund-us-or-stop-send...

        • justin_oaks 15 hours ago
          I read the linked article and can't find anything involving extortion; just that one person associated with the FFMPEG didnt like the flood of vulnerability reports.

          In fact, the article cites one of the FFMPEG maintainers as being grateful for the vulnerability reports.

          Did I miss something?

          • FabCH 14 hours ago
            Yes. You are missing the wider interpretation of the word extortion that includes obtaining benefit by coercion. Presumably you are only including extortion by use of blatantly illegal means in your definition. However, you don't need to threaten using illegal means to be extorting and/or blackmailing someone. You can be blackmailing someone by threatening to sue them in court, for example.

            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.

            • Diagon 2 hours ago
              As someone coming from the outside, it's astounding to me how oblivious so many in this discussion are to the obvious, ie. the question of power. Flip through a few texts on psychoanalysis, and you'll find this called "attacks on linking," always a from of motivated behavior.
        • fc417fc802 15 hours ago
          If google stops sending ffmpeg vulnerability reports the software will still be vulnerable but neither the maintainers nor the end users will be aware of it. As someone who makes use of ffmpeg I want google to continue sending such reports. If I'm running vulnerable software I very much want to know about it.
          • FabCH 14 hours ago
            You frequently transcode 40 year old Lucas Arts SCUMM VM videos?

            I would prefer ffmpeg team to have the time to focus on slightly newer stuff, as a user myself.

            • marshray 6 hours ago
              The problem is that the attacker gets to choose the codec that your device runs.
            • no-name-here 14 hours ago
              Does Google require ffmpeg to fix vulns? Per the GP commenter's point, isn't this just about whether people are eventually made aware of vulns?
              • FabCH 14 hours ago
                They require ffmpeg to respond in a Google controlled timeline.

                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.

                • ExoticPearTree 13 hours ago
                  > Just because the response can be "No", it doesn't mean Google didn't require _something_ from ffmpeg.

                  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".

                  • FabCH 13 hours ago
                    So, what if the project they are reporting to has a vulnerability disclosure project with 180 days notice?
                    • akerl_ 11 hours ago
                      Project Zero doesn’t care.

                      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.

                      • FabCH 6 hours ago
                        You might be surprised to learn that actually is illegal in some countries.

                        Famously, leaving reviews on TripAdvisor in Germany can get you sued.

                        • akerl_ 5 hours ago
                          You can be sued for anything.

                          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?

                          • fc417fc802 5 hours ago
                            Even if he managed to provide examples it would merely be demonstrating a restriction on the individual to openly speak his mind. Hardly something to celebrate.

                            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.

                            • akerl_ 4 hours ago
                              Project Zero is part of Google/Alphabet, which operates globally and has a legal presence in many countries. I can’t speak to where individuals on Project Zero are based.

                              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.

              • fc417fc802 14 hours ago
                Precisely. If it isn't worth fixing then don't fix it. As the end user I can then make an informed decision. If nothing else I'll know to thoroughly sandbox certain workloads if an unpatched CVE is applicable.
      • Devasta 11 hours ago
        > What do you think is the real motivation if not security?

        For a lot of security people its collecting scout badges.

    • FabCH 17 hours ago
      I agree with you. Google pretends that this is "donating security research to the community" and maybe it started like that, but it has been clear for some time that there is an element of bullying and abuse in the process that they are conveniently ignoring to be able to sleep better at night.

      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.

      • bmitc 16 hours ago
        That story is basically what I'm getting at, although I didn't know about that particular story. At a certain level of product, organization, and severity of bug, Google's threat to publish the vulnerability forces the hand of organizations to prioritize the fix since it will then be exposed. But that could be disruptive and unproductive, as the story you linked points out.
    • ExoticPearTree 13 hours ago
      > Is this a version of extortion?

      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.

  • aaabbbccccc 14 hours ago
    [flagged]
    • bluecalm 13 hours ago
      Slaves didn't have a choice what to work on. You are reward hunting. Reward hunting depends on both the size of promised reward as well as reliability of the counterparty to pay out. You seem to be misjudging the latter.
    • hbcdbff 12 hours ago
      You are suffering from AI psychosis
    • Natfan 12 hours ago
      comparing your choice to continue working with the slave trade is deeply insensitive to _actual_ enslaved people
      • AmazingEveryDay 12 hours ago
        Being enslaved is also deeply insensitive to enslaved people. A random comment on HN is likely least of worries.
  • jamiesonbecker 1 day ago
    [flagged]
    • Refreeze5224 1 day ago
      Nice unsolicited plug for your slop product.