The malicious changes were submitted by JiaT75, one of the two main xz Utils developers with years of contributions to the project.

“Given the activity over several weeks, the committer is either directly involved or there was some quite severe compromise of their system,” an official with distributor OpenWall wrote in an advisory. “Unfortunately the latter looks like the less likely explanation, given they communicated on various lists about the ‘fixes’” provided in recent updates. Those updates and fixes can be found here, here, here, and here.

On Thursday, someone using the developer’s name took to a developer site for Ubuntu to ask that the backdoored version 5.6.1 be incorporated into production versions because it fixed bugs that caused a tool known as Valgrind to malfunction.

“This could break build scripts and test pipelines that expect specific output from Valgrind in order to pass,” the person warned, from an account that was created the same day.

One of maintainers for Fedora said Friday that the same developer approached them in recent weeks to ask that Fedora 40, a beta release, incorporate one of the backdoored utility versions.

“We even worked with him to fix the valgrind issue (which it turns out now was caused by the backdoor he had added),” the Ubuntu maintainer said.

He has been part of the xz project for two years, adding all sorts of binary test files, and with this level of sophistication, we would be suspicious of even older versions of xz until proven otherwise.

  • Aux@lemmy.worldBannedBanned from community
    link
    fedilink
    English
    arrow-up
    13
    arrow-down
    49
    ·
    1 year ago

    And that’s why you cannot trust open source software blindly.

    • just_another_person@lemmy.world
      link
      fedilink
      English
      arrow-up
      13
      arrow-down
      1
      ·
      edit-2
      1 year ago

      You are an idiot. It’s not blind. That’s how it was found.

      Not having world accessible SSH is the real fix here.

      • Cosmic Cleric@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        ·
        1 year ago

        You are an idiot. It’s not blind. That’s how it was found.

        From the article…

        Will Dormann, a senior vulnerability analyst at security firm Analygence, said in an online interview. “BUT that’s only because it was discovered early due to bad actor sloppiness. Had it not been discovered, it would have been catastrophic to the world.”

        • 5C5C5C@programming.dev
          link
          fedilink
          English
          arrow-up
          7
          ·
          1 year ago

          The fact that it was discovered early due to bad actor sloppiness does not imply that it could not have also been caught prior to wide spread usage via security audits that take place for many enterprise grade Linux distributions.

          • just_another_person@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            arrow-down
            1
            ·
            1 year ago

            I think it does though. They call it sloppy, I call it sophisticated. Same reason they major distro is running checking shit out right now.

      • elshandra@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        Yeah I nearly panicked for a second there, then I remember noone’s getting near that anyway. Back to my relaxing weekend.

    • Takios@feddit.de
      link
      fedilink
      English
      arrow-up
      8
      ·
      edit-2
      1 year ago

      Imagine trying to make a helpdesk of a proprietary company take your “it’s taking 0.5 seconds longer to login” complaint seriously…

      • GreyEyedGhost@lemmy.ca
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        So many vulnerabilities were found due to time to login that one of the security features was to take longer to respond to a bad login so they couldn’t tell what part failed. Here’s an article I found about one such vulnerability.