public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca>
To: Cygwin Apps <cygwin-apps@cygwin.com>
Subject: Re: xz upstream backdoor compromise (was: Cygwin: Linux xz issue)
Date: Sat, 30 Mar 2024 02:08:33 -0600	[thread overview]
Message-ID: <d212a243-62e4-4247-988f-683e7db0847e@SystematicSW.ab.ca> (raw)
In-Reply-To: <em9acc6e7a-921f-4922-a5dd-77cc63657601@fece094b.com>

On 2024-03-29 16:43, Ron Murray via Cygwin wrote:
> 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.
> 
> References:
> https://www.cisa.gov/news-events/alerts/2024/03/29/reported-supply-chain-compromise-affecting-xz-utils-data-compression-library-cve-2024-3094
> https://access.redhat.com/security/cve/CVE-2024-3094
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-3094
> https://sysdig.com/blog/cve-2024-3094-detecting-the-sshd-backdoor-in-xz-utils/

	https://seclists.org/oss-sec/2024/q1/268

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer     but when there is no more to cut
                                 -- Antoine de Saint-Exupéry

           reply	other threads:[~2024-03-30  8:08 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <em9acc6e7a-921f-4922-a5dd-77cc63657601@fece094b.com>]

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=d212a243-62e4-4247-988f-683e7db0847e@SystematicSW.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin-apps@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).