• VitoRobles@lemmy.today
    link
    fedilink
    English
    arrow-up
    72
    ·
    2 days ago

    This is not surprising.

    The industry knowledge had by the thousands of engineers laid off has to go somewhere.

    • slazer2au@lemmy.world
      link
      fedilink
      English
      arrow-up
      80
      ·
      2 days ago

      Well when you report a bug to ms and they respond with disabing your account and you then release the 0day the ms responds with a public blog post saying people who release 0 days are breaking the law and liable for legal action of cause you then drop a second 0day and ms responds by retracing the legal threat so you you now drop a third one while your account to report these bugs is still disabled. What else would you do?

    • calcopiritus@lemmy.world
      link
      fedilink
      English
      arrow-up
      54
      ·
      edit-2
      2 days ago

      This is not about that. This is about a security researcher that wasn’t paid by Microsoft’s bug bounty program when they found a security bug.

      Bug bounty programs exist to prevent this exact scenario. To give people a reward for privately disclosing the vulnerability with the devs instead of publicly/to a bad actor.

      • Rothe@piefed.social
        link
        fedilink
        English
        arrow-up
        13
        ·
        edit-2
        2 days ago

        AMD fucked up recently about that as well. It seems big tech is getting so arrogant and so far up its own ass that they can’t even admit to bugs anymore, which is problematic considering their sloppy AI slop never had so many bugs as it does now.

        • P03 Locke@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          2
          ·
          2 days ago

          which is problematic considering their sloppy AI slop never had so many bugs as it does now.

          Honestly, it’s the opposite: AI is exposing so many bad security bugs that they are having a hard time keeping up.

          • mnemonicmonkeys@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 day ago

            That’s overblown. Yes, people are finding security bugs with AI, you will always get that when adding new tests with a different perspective. But the “having a hard time keeping up” come from the AI constantly spamming devs with duplicate issues.

              • mnemonicmonkeys@sh.itjust.works
                link
                fedilink
                English
                arrow-up
                3
                ·
                1 day ago

                This change is driven by a surge in CVE * submissions *, which increased 263% between 2020 and 2025.

                Emphasis mine.

                Your link doesn’t refute what I said. I acknowledged that there is an increase in bugs being found. That’s inevitable when you add a new tool.

                My argument is that the framing is overblown. Sure, the submissions increased 263%, but how many of those are duplicate issues? Is it more like a 22% increase in actual bugs being found, with each being duplicated a dozen times of average? Big numbers are what get attention, but when you only frame an argument around the big number you lose a lot of the context.

                I recall either Lutris or Heroic games launcher actually seeing a (probably temporary) spike in bugs being found due to AI, but they were getting swamped by the same bugs being reported over and over in a short timespan. Each of those reports need to be looked over with the same amount of scrutiny, so flooding a repository with duplicate issues becomes a major drain on dev resources.

                Also, working in software myself, you always see a spike in issues when you first add a new test or check to your code. Then as you resolve those issues they drop back down. That’s not that different from what we’re seeing here with AI bug reporting