this post was submitted on 29 Mar 2024
669 points (99.0% liked)

Technology

59223 readers
3154 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
 

The malicious changes were submitted by JiaT75, one of the two main xz Utils developers with years of contributions to the project.

“Given the activity over several weeks, the committer is either directly involved or there was some quite severe compromise of their system,” an official with distributor OpenWall wrote in an advisory. “Unfortunately the latter looks like the less likely explanation, given they communicated on various lists about the ‘fixes’” provided in recent updates. Those updates and fixes can be found here, here, here, and here.

On Thursday, someone using the developer's name took to a developer site for Ubuntu to ask that the backdoored version 5.6.1 be incorporated into production versions because it fixed bugs that caused a tool known as Valgrind to malfunction.

“This could break build scripts and test pipelines that expect specific output from Valgrind in order to pass,” the person warned, from an account that was created the same day.

One of maintainers for Fedora said Friday that the same developer approached them in recent weeks to ask that Fedora 40, a beta release, incorporate one of the backdoored utility versions.

“We even worked with him to fix the valgrind issue (which it turns out now was caused by the backdoor he had added),” the Ubuntu maintainer said.

He has been part of the xz project for two years, adding all sorts of binary test files, and with this level of sophistication, we would be suspicious of even older versions of xz until proven otherwise.

you are viewing a single comment's thread
view the rest of the comments
[–] DAMunzy@lemmy.dbzer0.com 44 points 7 months ago* (last edited 7 months ago) (3 children)

A stable release of Arch Linux is also affected. That distribution, however, isn't used in production systems.

Shots fired!

It seems WSL Ubuntu and Kali are safe with versions 5.2.5 and 5.4.4 installed respectfully.

[–] anlumo@lemmy.world 11 points 7 months ago (2 children)

Damn, I installed mine disrespectful.

[–] Zink@programming.dev 1 points 7 months ago

Is that when you install it in a VM, as if to show it that it’s not a good enough little distro to boot directly on your hardware?

I suddenly feel so guilty!

[–] DAMunzy@lemmy.dbzer0.com 1 points 7 months ago

I thought about the same (disrespectful) as I typed it. I've already laughed with you!

Don't forget about openSUSE Tumbleweed! It's actually affected AFAIK.

[–] HarriPotero@lemmy.world -2 points 7 months ago* (last edited 7 months ago) (3 children)

I think the AI that wrote the article misunderstood.

Arch doesn't build from release tar balls, but straight from git. Arch also doesn't link sshd against liblzma. So while they've shipped the dirty version of xz utils, at least sshd is not affected.

It's possible that the dirty version affected some of the other things that link liblzma. Like a handful of kde components for example.

[–] d13@programming.dev 36 points 7 months ago (2 children)

the AI that wrote the article

The linked article is by Dan Goodin from Ars Technica. He's not immune to mistakes, but he's been writing good articles about security for years.

Can we please not accuse everybody of being AI just because they made a mistake?

[–] chtk@feddit.nl 16 points 7 months ago

Can we please not accuse everybody of being AI

Suspicious. /s

[–] jj4211@lemmy.world 7 points 7 months ago

Also, the malicious code only activated if it detected being built as dpkg or rpm.