If you’re running version 5.6.0 or 5.6.1, downgrade immediately.

23 points

Do not run xz --version. Instead check the version in your package manager.

permalink
report
reply
14 points
*
debian/ubuntu based distros:
apt show xz-utils
or
dpkg -l | grep xz

redhat/fedora-based:
yum info xz
dnf info xz

arch-based:
pacman -Qi xz

EDIT: correction as suggested below

permalink
report
parent
reply
3 points

On my machine the package name is slightly different:

apt show xz-utils

permalink
report
parent
reply
2 points

5.4.1, my habit of putting off updates pays off again

permalink
report
parent
reply
6 points

Why is that? I know the latter gives you more info, but it’s still the same thing isn’t it?

permalink
report
parent
reply
20 points

Because you are running the affected software. It’s a bad idea to run something if we are aware that it contains or relies on malicious code.

permalink
report
parent
reply
15 points

Omg obviously. Can’t believe I didn’t realize that. Thanks for the answer.

permalink
report
parent
reply
17 points

Wow! This was so close to perhaps being one of the worst security compromises in open source history.

permalink
report
reply
12 points

For me I feel like we have not had any big security stuff since the whole log4j thing. While this seems bigger they have caught it relatively early. I feel like more people had to panic patch Minecraft servers with log4j.

permalink
report
parent
reply
7 points

maybe the libwebp vulnerability deserves a honorable mention, although i don’t think it has had as big an impact, it could’ve been way worse.

permalink
report
parent
reply
4 points

Good point! I did forget about that one.

permalink
report
parent
reply
6 points

My only reservation is that this compromised contributor has been working on the project for a few years. I hope that this is the end of the tunnel and there aren’t more issues to be uncovered with further analysis.

permalink
report
parent
reply
12 points

Its easy to spiral out of control thinking about how the practice that got us this backdoor is something that is used all over the open source community to build code. In the end we can only evaluate what is in front of us and pray the things lurking in the shadows are something we can deal with when they expose themselves.

permalink
report
parent
reply
16 points

Jokes on you; I haven’t run a system update since 2006

permalink
report
reply
2 points

Ubuntu 6.06 moment (Debian 3.1)

permalink
report
parent
reply
3 points

I’m using arch btw. … oh no

permalink
report
parent
reply
16 points

Mods should sticky this. This is the third post in this comm about the vulnerability.

permalink
report
reply
6 points
*

The only people who will have this vulnerability AFAIK (and have it be actionable with the ssh backdoor) are folks running Debian unstable on a ssh server. The shitty part about this is a rupture in trust for the maintainers at xz.

Honestly, the attacker picked a really shitty time frame considering their payload isn’t in any important point releases where they could have the most effect.

permalink
report
parent
reply
14 points
*

How to check your version without running xz on nixOS, the official OS of trans people:

ls -l $(which xz)

I’m at 5.4.4 thankfully.

permalink
report
reply
6 points

nixos doesn’t appear to be vulnerable in general, based on this thread

permalink
report
parent
reply

technology

!technology@hexbear.net

Create post

On the road to fully automated luxury gay space communism.

Spreading Linux propaganda since 2020

Rules:

  • 1. Obviously abide by the sitewide code of conduct. Bigotry will be met with an immediate ban
  • 2. This community is about technology. Offtopic is permitted as long as it is kept in the comment sections
  • 3. Although this is not /c/libre, FOSS related posting is tolerated, and even welcome in the case of effort posts
  • 4. We believe technology should be liberating. As such, avoid promoting proprietary and/or bourgeois technology
  • 5. Explanatory posts to correct the potential mistakes a comrade made in a post of their own are allowed, as long as they remain respectful
  • 6. No crypto (Bitcoin, NFT, etc.) speculation, unless it is purely informative and not too cringe
  • 7. Absolutely no tech bro shit. If you have a good opinion of Silicon Valley billionaires please manifest yourself so we can ban you.

Community stats

  • 1.7K

    Monthly active users

  • 1.3K

    Posts

  • 17K

    Comments