How the xz backdoor highlights a major flaw in Nix | Shade's Blog
shadeyg56.vercel.app
Background On Friday, March 29th, 2024, a historical and sophisticated security vulnerability (CVE-2024-3094) was discovered in the XZ Utils package and liblzma api in version 5.6.0 and 5.6.1. While this vulnerability mostly affects Debian and RedHat distributions, there was some interesting discussion regarding xz and Nix. How did this affect Nix and NixOS? The truth is not a whole lot in reality. I saw conflicting reports, but supposedly, the tarballs of xz that Nix downloads were not infected.

The main issue is the handling of security updates within the Nixpkgs ecosystem, which relies on Nix’s CI system, Hydra, to test and build packages. Due to the extensive number of packages in the Nixpkgs repository, the process can be slow, causing delays in the release of updates. As an example, the updated xz 5.4.6 package took nearly 5 days to become available in the unstable branch!

Fundamentally, there needs to be a change in how security fixes are handled in Hydra. As stated in the article, Nix was lucky to be unaffected, but multiple days to push out a security patch of this severity is concerning, even if there was no reason for concern.

  • delirious_owl@discuss.online
    81·
    8 months ago

    This means users such as myself who use the unstable branch for all of their packages will still be pulling the (potentially) infected xz tarballs onto their machines!

    Yeah dont do that. On any OS that’s asking for problems.

    • kent_eh@lemmy.caEnglish
      51·
      8 months ago

      Exactly. If you want to live on the bleeding edge, you have to accept that there will be risks.

      Nobody should be running their main/only/mission critical machine on an unstable branch of any software.

      It’s literally in the name unstable.