All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Marcus Hoffmann <marcus.hoffmann@othermo.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/gzip: security bump to 1.12
Date: Sun, 22 May 2022 12:30:59 +0200	[thread overview]
Message-ID: <875ylxzwnw.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220419111714.1647112-1-marcus.hoffmann@othermo.de> (Marcus Hoffmann's message of "Tue, 19 Apr 2022 13:17:13 +0200")

>>>>> "Marcus" == Marcus Hoffmann <marcus.hoffmann@othermo.de> writes:

 > Fixes the following security issues:
 > CVE-2022-1271: arbitrary-file-write vulnerability

 > zgrep applied to a crafted file name with two or more newlines
 > can no longer overwrite an arbitrary, attacker-selected file.
 > [bug introduced in gzip-1.3.10]

 > https://www.openwall.com/lists/oss-security/2022/04/07/8

 > Other changes:

 > ** Changes in behavior

 >   'gzip -l' no longer misreports file lengths 4 GiB and larger.
 >   Previously, 'gzip -l' output the 32-bit value stored in the gzip
 >   header even though that is the uncompressed length modulo 2**32.
 >   Now, 'gzip -l' calculates the uncompressed length by decompressing
 >   the data and counting the resulting bytes.  Although this can take
 >   much more time, nowadays the correctness pros seem to outweigh the
 >   performance cons.

 >   'zless' is no longer installed on platforms lacking 'less'.

 > ** Bug fixes

 >   zgrep now names input file on error instead of mislabeling it as
 >   "(standard input)", if grep supports the GNU -H and --label options.

 >   'zdiff -C 5' no longer misbehaves by treating '5' as a file name.
 >   [bug present since the beginning]

 >   Configure-time options like --program-prefix now work.

 > Release Announcement:
 > https://lists.gnu.org/r/bug-gzip/2022-04/msg00011.html

 > Signed-off-by: Marcus Hoffmann <marcus.hoffmann@othermo.de>

Committed to 2022.02.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2022-05-22 10:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-19 11:17 [Buildroot] [PATCH 1/2] package/gzip: security bump to 1.12 Marcus Hoffmann
2022-04-19 11:17 ` [Buildroot] [PATCH 2/2] package/xz: backport CVE-2022-1271 security fix Marcus Hoffmann
2022-04-19 16:47   ` Baruch Siach via buildroot
2022-04-19 17:27     ` Marcus Hoffmann
2022-04-19 17:37     ` Marcus Hoffmann
2022-04-19 20:31 ` [Buildroot] [PATCH 1/2] package/gzip: security bump to 1.12 Arnout Vandecappelle
2022-05-22 10:30 ` Peter Korsgaard [this message]

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=875ylxzwnw.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=marcus.hoffmann@othermo.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.