this post was submitted on 29 Mar 2024
671 points (100.0% liked)

Technology

68526 readers
3253 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 news or articles.
  3. Be excellent to each other!
  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, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years 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
[–] [email protected] 114 points 1 year ago (1 children)

And yet with closed-source software you have no choice but to trust it blindly. At least open source software has people looking at the code.

[–] TheKMAP 5 points 1 year ago (2 children)

Bet you anything there were more pairs of eyes on SolarWinds code than this. Sick of this open source bystander effect.

Code scanners check for vulnerabilities not malicious code. Ain't no one running full coverage dynamic scanners to trigger all branches of code on this thing, otherwise this would've been caught immediately

[–] [email protected] 15 points 1 year ago* (last edited 1 year ago) (2 children)

Vulnerabilities are caught and fixed faster in open source projects than closed ones.

The researchers found that open-source programmers fixed Linux issues in an average of only 25 days. In addition, Linux's developers have been improving their speed in patching security holes from 32 days in 2019 to just 15 in 2021.

Its competition didn't do nearly as well. For instance, Apple, 69 days; Google, 44 days; and Mozilla, 46 days.

Coming in at the bottom was Microsoft, 83 days, and Oracle with 109 days.

By Project Zero's count, others, which included primarily open-source organizations and companies such as Apache, Canonical, Github, and Kubernetes, came in with a respectable 44 days.

[–] [email protected] 5 points 1 year ago

Intel: 24 years

[–] TheKMAP 2 points 1 year ago (1 children)

Your data is about remediation speed not thoroughness of discovery.

[–] [email protected] 2 points 1 year ago

FOSS is substantially faster in both.

[–] [email protected] 3 points 1 year ago (1 children)

There is, it’s Google Fuzz which the maintainer of XZ handily disabled the codeshare for.

[–] TheKMAP 1 points 1 year ago (1 children)

Interesting! When? Maybe that can be a metric or requirement before companies or seriously popular projects consider importing upstream code.

[–] [email protected] 1 points 1 year ago (1 children)
[–] TheKMAP 1 points 1 year ago

https://github.com/google/oss-fuzz/pull/10667#pullrequestreview-1518981986

Looks like it was a cover up attempt to prevent manual attention and would not have been caught by the automation.