From: Achim Gratz <Stromeko@Nexgo.DE>
To: cygwin@cygwin.com
Subject: Re: Linux xz issue
Date: Sat, 30 Mar 2024 11:14:53 +0100 [thread overview]
Message-ID: <uu8omt$tdd$1@ciao.gmane.io> (raw)
In-Reply-To: <em9acc6e7a-921f-4922-a5dd-77cc63657601@fece094b.com>
Am 29.03.2024 um 23:43 schrieb Ron Murray via Cygwin:
> There is a serious security issue with xz (and liblzma) versions 5.6.0-1
> and 5.6.1-1. I note that cywin currently is suggesting an upgrade to
> 5.6.1-1, which is unsafe. I've looked at the cygwin archives and I don't
> see a reference to this: sorry if you're already aware of this issue.
Based on what I know so far (and I can't check in detail right now)
Cygwin is likely not affected: it isn't Linux, nor does it use glibc or
systemd and also not the patch for OpenSSH that allows the backdoor to
get activated. So, the code injection into liblzma5 has very likely not
been performed during the build (I will check that, but it will take a
week or so) and even if it did it could not work on Cygwin.
Beyond that, the version 5.4.6 that everybody is currently reverting to
(and is also still available for Cygwin if you want to go back) was
already released when the presumed bad actor was co-maintainer and their
involvement goes back even farther based on the Xz developer mailing
list. The repository has been deactivated by GitHub so I can't check
there, but there is already some discussion about rolling back to 5.3.1
or thereabouts.
Please note that the account in question has also landed some code in
libarchive which is likely going to get reverted. From the looks of it
there were a few sock-puppet accounts that were supporting the
activities and it remains to be seen where else these might turn up.
--
Achim.
(on the road :-)
next prev parent reply other threads:[~2024-03-30 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 22:43 Ron Murray
2024-03-30 10:14 ` Achim Gratz [this message]
2024-04-01 4:15 Keith Thompson
2024-04-01 8:11 ` Keith Thompson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='uu8omt$tdd$1@ciao.gmane.io' \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).