▲ 520 ▼ backdoor in upstream xz/liblzma leading to ssh server compromise (www.openwall.com) submitted 2 years ago by Atemu@lemmy.ml to c/linux@lemmy.ml 96 comments fedilink hide all child comments
[–] corsicanguppy@lemmy.ca 5 points 2 years ago (3 children) when building RPM or DEB. Which ones? Everything I run seems to be clear. https://access.redhat.com/security/cve/CVE-2024-3094 | Products / Services | Components | State | | | | | | Enterprise Linux 6 | xz | Not affected | | Enterprise Linux 7 | xz | Not affected | | Enterprise Linux 8 | xz | Not affected | | Enterprise Linux 9 | xz | Not affected | (and thus all the bug-for-bug clones) permalink fedilink source parent hideshow 6 child comments replies: [–] progandy@feddit.de 3 points 2 years ago Those getting the most recent software versions, so nothing that should be running in a server. permalink fedilink source parent [–] Laser@feddit.de 2 points 2 years ago Fedora 41, Fedora Rawhide, Debian Sid are the currently known affected ones AFAIK. permalink fedilink source parent [–] flying_sheep@lemmy.ml 1 point 2 years ago I think it needs to be rolling release (because it was caught so quickly that it hasn't made its way into any cadence based distro yet) using the upstream Makefile task to build a RPM or DEB (because the compromised build script directly checks for that and therefore doesn't trigger for a destdir build like Gentoo’s or Arch’s) using the upstream provided tarball as opposed to the one GitHub provides, or a git clone (because only that contains the compromised Makefile, running autotools yourself is safe) Points 1 and 2 mean that only rolling release RPM and DEB distros like Debian Sid and Fedora are candidates. I didn't check if they use the Makefile and the compromised tarballs. permalink fedilink source parent
[–] progandy@feddit.de 3 points 2 years ago Those getting the most recent software versions, so nothing that should be running in a server. permalink fedilink source parent
[–] Laser@feddit.de 2 points 2 years ago Fedora 41, Fedora Rawhide, Debian Sid are the currently known affected ones AFAIK. permalink fedilink source parent
[–] flying_sheep@lemmy.ml 1 point 2 years ago I think it needs to be rolling release (because it was caught so quickly that it hasn't made its way into any cadence based distro yet) using the upstream Makefile task to build a RPM or DEB (because the compromised build script directly checks for that and therefore doesn't trigger for a destdir build like Gentoo’s or Arch’s) using the upstream provided tarball as opposed to the one GitHub provides, or a git clone (because only that contains the compromised Makefile, running autotools yourself is safe) Points 1 and 2 mean that only rolling release RPM and DEB distros like Debian Sid and Fedora are candidates. I didn't check if they use the Makefile and the compromised tarballs. permalink fedilink source parent