this post was submitted on 08 Apr 2024
69 points (90.6% liked)

Linux

48031 readers
797 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
nooter692@lemmy.ml
AgreeableLandscape@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz
69
Is xz 5.6.1-3+ still dangerous? (lemmy.ml)
submitted 7 months ago* (last edited 6 months ago) by GolfNovemberUniform@lemmy.ml to c/linux@lemmy.ml
53 comments fedilink hide all child comments
 

When the xz backdoor was discovered, I quickly uninstalled my Arch based setup with an infected version of the software and switched to a distro that shipped an older version (5.5 or 5.4 or something). I found an article which said that in 5.6.1-3 the backdoor was "fixed" by just not letting the malware part communicating with the vulnerable ssh related stuff and the actual malware is still there? (I didn't understand 80% of the technical terms and abbreviations in it ok?) Like it still sounds kinda dangerous to me, especially since many experts say that we don't know the other ways this malware can use (except for the ssh supply chain) yet. Is it true? Should I stick with the new distro for now or can I absolutely safely switch back and finally say that I use Arch btw again?

P. S. I do know that nothing is completely safe. Here I'm asking just about xz and libxzlk or whatever the name of that library is

EDIT: 69 upvotes. Nice

you are viewing a single comment's thread
view the rest of the comments
[–] rtxn@lemmy.world 36 points 7 months ago* (last edited 7 months ago) (1 children)

TL;DR: starting with 5.6.1-2, XZ is safe on Arch. Safe as in not affected by this particular vulnerability.

Look here: https://gitlab.archlinux.org/archlinux/packaging/packages/xz/-/commit/881385757abdc39d3cfea1c3e34ec09f637424ad

And here: https://security.archlinux.org/ASA-202403-1

5.6.1-2 is where the package switched from building from the tarball (backdoored) to the upstream git repo (clean). The tarball release contained some extra build instructions (which didn't exist in the git repo) that added the backdoor during the build process. The issue arose from the downstream maintainers' assumption that the contents of the tarball and the git repo were identical.

Subsequent changes, and 5.6.1-3, were mostly administrative, like changing the git repository's URL (since the maintainer's github account was banned) and locking out Jia Tan's PGP key.

an article which said that in 5.6.1-3 the backdoor was “fixed” by just not letting the malware part communicating with the vulnerable ssh related stuff

That article is bullshit, don't believe a thing it says. Arch was not affected by the SSH vulnerability because the sshd binary did not link liblzma where the backdoor existed, so they could never communicate in a way that could be exploited by this particular vulnerability. It was not part of the fix.

[–] GolfNovemberUniform@lemmy.ml 2 points 7 months ago (1 children)

5.6.1-2 is where the package switched from building from the tarball (backdoored) to the upstream git repo (clean)

This is what I was looking for. Though if 5.6.1-2 doesn't contain the backdoor, why is it listed as the last version that does contain it everywhere?

[–] rtxn@lemmy.world 6 points 7 months ago* (last edited 7 months ago) (1 children)

why is it listed as the last version that does contain it everywhere?

I don't know, but the official advisory is most likely to be correct. Everything else is a game of Chinese whispers where the information becomes less reliable the more it is passed on. Maybe it's because -2 still had Jia Tan's signing key, and could have, theoretically, accepted commits signed by them.

Where is it listed as such? Can you give examples?

[–] GolfNovemberUniform@lemmy.ml 0 points 7 months ago

Hmm I looked it up and I'm either searching it wrong or it seems like the articles were edited and the stuff about 5.6.1-2 being infected is deleted. I think you're right about the keys. That could be the reason for yellow press to exaggerate the problem