• agent_flounder@lemmy.world
    link
    fedilink
    English
    arrow-up
    15
    ·
    7 months ago

    Yeah it sounds pretty wild already with some kind of, like, door knock mechanism using certificates? So you can’t scan for it. And some reverse engineering countermeasures.

    Like everyone else, I have to wonder what libraries have been compromised in a way that nobody has noticed yet.

    • Fubarberry@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      5
      ·
      7 months ago

      Yeah, that’s the scariest part. This was caught, but are there other projects out there that have been attacked with similar methods that no one knows about?

      • trolololol@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        7 months ago

        There’s also the ones known by very few people. There’s companies and unofficial groups of people who collect and sell this information. Usually to state governments, off records.

        I don’t think it’s the case for Linux, but I occasionally follow the state of things for bounties offered by Google and Apple to white hat hackers. Though this case is clearly malicious, I understand most vulnerabilities can easily pass as a bug/mistake.

    • damium@programming.dev
      link
      fedilink
      English
      arrow-up
      2
      ·
      7 months ago

      From what I’ve read is not authentication bypass, it’s a RCE using certificates to deliver the payload. If a specific signature is found it runs the code that was sent in place of the signing public key. It also means that only someone who has the ability to generate that specific key signature could use the RCE.

      There were some other bits that looked like they could have been placed to enable compromising other build systems in the future when they checked for xz support.