backdoor in upstream xz/liblzma leading to ssh server compromisewww.openwall.comcross-posted to: technologie@jlai.lunetsec@links.hackliberty.orgprogramming@programming.devhackernews@lemmy.smeargle.fanssecurity@lemmy.ml Atemu ( @Atemu@lemmy.ml ) Linux@lemmy.ml • 3 months ago message-square70fedilinkarrow-up1337
arrow-up1337external-linkbackdoor in upstream xz/liblzma leading to ssh server compromisewww.openwall.com Atemu ( @Atemu@lemmy.ml ) Linux@lemmy.ml • 3 months ago message-square70fedilinkcross-posted to: technologie@jlai.lunetsec@links.hackliberty.orgprogramming@programming.devhackernews@lemmy.smeargle.fanssecurity@lemmy.ml
minus-square SavvyBeardedFish ( @SavvyBeardedFish@reddthat.com ) linkfedilinkEnglish12•3 months agoArchlinux’s XZ was compromised as well. News post Git change for not using tarballs from source
minus-square flying_sheep ( @flying_sheep@lemmy.ml ) linkfedilink10•3 months agoNo, read the link you posted: 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: ldd "$(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.
minus-square progandy ( @progandy@feddit.de ) linkfedilink5•edit-23 months agoI think that was a precaution. The malicious build script ran during the build, but the backdoor itself was most likely not included in the resuling package as it checked for specific packaging systems. https://www.openwall.com/lists/oss-security/2024/03/29/22
Archlinux’s XZ was compromised as well.
News post
Git change for not using tarballs from source
No, read the link you posted:
I think that was a precaution. The malicious build script ran during the build, but the backdoor itself was most likely not included in the resuling package as it checked for specific packaging systems.
https://www.openwall.com/lists/oss-security/2024/03/29/22