Technology

59135 readers

3561 users here now

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

Our Rules

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

Approved Bots

founded 1 year ago

MODERATORS

671

Backdoor found in widely used Linux utility breaks encrypted SSH connections (arstechnica.com)

submitted 7 months ago by Hubi@feddit.de to c/technology@lemmy.world

190 comments fedilink hide all child comments

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

[–] Buelldozer@lemmy.today 88 points 7 months ago* (last edited 7 months ago) (2 children)

Jia Tan, University of Hong Kong in China. He’s been the sole maintainer of the package for almost two years.

[–] Dark_Arc@social.packetloss.gg 86 points 7 months ago (1 children)

Looks like he'd done a lot for various US companies on his LinkedIn.

I would not be surprised if he was previously legit but pressured into doing this by the CCP.

[–] Takios@feddit.de 29 points 7 months ago (1 children)

Maybe he wasn't sloppy by accident if he was indeed coerced by someone. I don't think we'll ever find out the backstory of this though.

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

I’ve watched a rundown of what the backdoor does. It’s impossible that this was an accident. It hides a compiled library in test data and injects that into the ssh binary to override code there.

[–] ghterve@lemmy.world 10 points 7 months ago* (last edited 7 months ago)

They didn't mean the backdoor was (or was not) an accident. They meant the backdoor was implemented sloppily enough to be discovered and maybe that was not an accident (as in, he wanted it to be found, but still wanted to plausibly be seen as trying his best to keep those coercing him appeased)

[–] WhatAmLemmy@lemmy.world 32 points 7 months ago (1 children)

It would make more sense to compromise developers in trusted positions, or steal their credentials, than going through the time and effort of building trusted users and projects only to burn them with easily spotted vulnerabilities.

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

This wasn't easily spotted. They use words like sloppy, but it all started with someone digging in because starting ssh season was about a half second slower that it used to be. I could easily imagine 99.99% of people shrugging and deciding just something in the chain of session startup took a bit longer for a reason not worth digging into.

Also, this was a maintainer that just started two years ago. xz is much older than that, just he took over.