Atemu to Linux • 2 months agobackdoor in upstream xz/liblzma leading to ssh server compromisewww.openwall.commessage-square100arrow-up1528arrow-down15cross-posted to: technologie@jlai.luselfhosted@lemmy.worldlinux@lemmy.worldnetsec@lemmy.worldprogramming@programming.devsaugumas@group.ltcybersecurity@sh.itjust.workshackernews@lemmy.smeargle.fanssecurity
arrow-up1523arrow-down1external-linkbackdoor in upstream xz/liblzma leading to ssh server compromisewww.openwall.comAtemu to Linux • 2 months agomessage-square100cross-posted to: technologie@jlai.luselfhosted@lemmy.worldlinux@lemmy.worldnetsec@lemmy.worldprogramming@programming.devsaugumas@group.ltcybersecurity@sh.itjust.workshackernews@lemmy.smeargle.fanssecurity
minus-square@SavvyBeardedFish@reddthat.comlinkfedilinkEnglish17•2 months agoArchlinux’s XZ was compromised as well. News post Git change for not using tarballs from source
minus-square@flying_sheeplink13•2 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@feddit.delinkfedilink3•edit-22 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