TL;DR there was a backdoor found in the XZ program. All major distros have been updated but it is recommended that you do a fresh install on systems that are exposed to the internet and that had the bad version of the program. Only upstream distros were affected.

all 42 comments

sorted by: hot top controversial new old
[–] 111 points 2 years ago (13 children)

stable release of Arch Linux is also affected. That distribution, however, isn't used in production systems.

Don't tell me how to live my life, Ars Technica.

  • source
  • hideshow 13 child comments
  • [–] 38 points 2 years ago (3 children)
  • [–] 42 points 2 years ago (1 child)

    They mean a variant you use in a stable, like to run an automatic feeder for horses. According to Ars Technica, however, you are not to use it in your production stable.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 12 points 2 years ago

    Yeah, screw em. I use mine to produce lots of stuff.
    I try to avoid producing too much manure though.

    I think lots of IT people have an extremely limited experience of what it is to produce something.
    I mean if opening a ssh hole to the whole world to fuck with is an important part of what they consider "production" - well I'm not really into those types of websites.

  • source
  • parent
  • [–] 21 points 2 years ago

    I am not deep enough in it, but from the arch-announce mailinglist:

    From the upstream report [1]:

    openssh does not directly use liblzma. However debian and several other distributions patch openssh to support systemd notification, and libsystemd does depend on lzma.

    Arch does not directly link openssh to liblzma, and thus this attack vector is not possible. You can confirm this by issuing the following command:

    $(command -v sshd)
    

    However, out of an abundance of caution, we advise users to remove the malicious code from their system by upgrading either way. This is because other yet-to-be discovered methods to exploit the backdoor could exist.

    https://www.openwall.com/lists/oss-security/2024/03/29/4

  • source
  • parent
  • [–] [S] 17 points 2 years ago (6 children)

    You should not run Arch in production. Boom, I said it

  • source
  • parent
  • hideshow 6 child comments
  • [–] 30 points 2 years ago (5 children)
  • [–] 9 points 2 years ago (4 children)
  • [–] 37 points 2 years ago (3 children)
  • [–] 43 points 2 years ago (1 child)

    This was basically a lucky catch. Sadly makes you wonder how many backdoors like that have not been found (yet). Never the less the distro model of not feeding in upstream binaries directly is an important part of the multi-barrier security.

  • source
  • hideshow 1 child comment
  • [–] 25 points 2 years ago

    Catching this now is pretty huge, because it mainly targets distro build systems. Had this gone undetected, we'd be in shiznit creek couple of years down the line.

  • source
  • [–] 13 points 2 years ago (4 children)

    For those on Android running Termux, it is also affected. Just checked my version of xz-utils and it was 5.6.1. Running "pkg upgrade" will roll back to version 5.4.5 (tagged as "5.6.1+really5.4.5" for both liblzma and xz-utils packages).

  • source
  • hideshow 4 child comments
  • [–] [S] 7 points 2 years ago (1 child)

    Makes you wonder why Termux ships the latest stuff. It might be smart to allow more time for critical problems to get caught.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 9 points 2 years ago*

    Probably for the exact same reason this backdoor was introduced. Users complain about slow feature rollouts so (unpaid) devs (maintaining software in their spare time out of the kindness of their hearts) cut corners. In some situations that looks like bringing on a second maintainer without thorough vetting, in others it looks like importing upstream packages without thorough vetting.

    Don't blame the Termux devs here, blame the community that keeps pushing them to move faster.

  • source
  • parent
  • [–] [B] 10 points 2 years ago

    This is the best summary I could come up with:


    Researchers have found a malicious backdoor in a compression tool that made its way into widely used Linux distributions, including those from Red Hat and Debian.

    An update the following day included a malicious install script that injected itself into functions used by sshd, the binary file that makes SSH work.

    So-called GIT code available in repositories aren’t affected, although they do contain second-stage artifacts allowing the injection during the build time.

    In the event the obfuscated code introduced on February 23 is present, the artifacts in the GIT version allow the backdoor to operate.

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

    The malicious versions, researchers said, intentionally interfere with authentication performed by SSH, a commonly used protocol for connecting remotely to systems.


    The original article contains 810 words, the summary contains 146 words. Saved 82%. I'm a bot and I'm open source!

  • source
  • [–] 6 points 2 years ago (8 children)

    Just makes you wonder what else (if anything) is backdoored. I am seriously 🤏 this close to just switching all of my boxes over to OpenBSD.

    The last time someone over there was approached about backdooring a related piece of software (which they refused), the OpenBSD devs manually screened the entire codebase, just in case something got in.

    Really, the only things I'd miss would be Minecraft, KDE, and Mullvad Browser; and of course I'd have to buy a couple more WiFi dongles (or learn how to port drivers from Linux).

  • source
  • hideshow 8 child comments
  • [–] [S] 6 points 2 years ago (6 children)

    I honestly think BSD has the potential to be worse due lack of people. I think the best option is to not be paranoid as a user. If someone needs to be paranoid it is the maintainers.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 1 point 2 years ago (5 children)

    I think the best option is to not be paranoid as a user.

    Yeah, just never be a dissident, or a whistleblower, or an activist, or a member of a vulnerable marginalized group. Remember, if you obey there's no reason to fear being spied on.

    I really don't think you understand how serious this kind of backdoor is. It puts certain people in real danger.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 1 point 2 years ago (1 child)

    And I don't think you understand OPs point. Of course you should be paranoid as a person like that, but most users aren't targets. If you, as a regular user, get this paranoid about using computers, maybe you should evaluate your priorities.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 2 years ago

    If you, as a regular user, get this paranoid about using computers, maybe you should evaluate your priorities.

    "Regular user" seems to be a strange counter to all the people I just listed that would be affected here. I'm not worried about myself, I'm worried about the people whose privacy and security is extremely important in this context.

  • source
  • parent
  • [–] [S] -1 points 2 years ago (2 children)

    These people do not seem to be affected unless they run Arch for some reason.

  • source
  • parent
  • hideshow 2 child comments
  • [+] -33 points 2 years ago (9 children)

    Meanwhile non SystemD systems like NetBSD FreeBSD OpenBSD are safer.

  • source
  • hideshow 9 child comments
  • [–] 19 points 2 years ago (3 children)

    What does this have to do with systemd? Aren't they safer in this situation because they aren't using the beta xz release?

    My systems running Debian stable with systemd also aren't affected...

  • source
  • parent
  • hideshow 3 child comments
  • [–] 11 points 2 years ago (1 child)

    This particular backdoor affects sshd on systems that use libsystemd for logging.

    your Debian system is probably not affected because Debian stable doesn't update packages very quickly. You're probably on an older release of the backdoored package.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 4 points 2 years ago

    The reason openssh links liblzma in the first place is to enable a systemd feature, so naturally "systemd bad, it's proximity to a security issue is yet more proof that a pile of shell scripts in a trenchcoat is a superior init system" etc

  • source
  • parent