All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: Marcus Hoffmann <marcus.hoffmann@othermo.de>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/gzip: security bump to 1.12
Date: Tue, 19 Apr 2022 22:31:19 +0200	[thread overview]
Message-ID: <087b047b-348d-cd25-8f40-4a551851c38b@mind.be> (raw)
In-Reply-To: <20220419111714.1647112-1-marcus.hoffmann@othermo.de>



On 19/04/2022 13:17, Marcus Hoffmann wrote:
> 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>

  Applied to master, thanks.

  Regards,
  Arnout

> ---
>   package/gzip/gzip.hash | 4 ++--
>   package/gzip/gzip.mk   | 2 +-
>   2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/package/gzip/gzip.hash b/package/gzip/gzip.hash
> index 1cf73ff912..80b86f4797 100644
> --- a/package/gzip/gzip.hash
> +++ b/package/gzip/gzip.hash
> @@ -1,6 +1,6 @@
>   # Locally calculated after checking pgp signature
> -# https://ftp.gnu.org/gnu/gzip/gzip-1.11.tar.xz.sig
> +# https://ftp.gnu.org/gnu/gzip/gzip-1.12.tar.xz.sig
>   # using key 155D3FC500C834486D1EEA677FD9FCCB000BEEEE
> -sha256  9b9a95d68fdcb936849a4d6fada8bf8686cddf58b9b26c9c4289ed0c92a77907  gzip-1.11.tar.xz
> +sha256  ce5e03e519f637e1f814011ace35c4f87b33c0bbabeec35baf5fbd3479e91956  gzip-1.12.tar.xz
>   # Locally calculated
>   sha256  8ceb4b9ee5adedde47b31e975c1d90c73ad27b6b165a1dcd80c7c545eb65b903  COPYING
> diff --git a/package/gzip/gzip.mk b/package/gzip/gzip.mk
> index 92588fcdb8..2092df363c 100644
> --- a/package/gzip/gzip.mk
> +++ b/package/gzip/gzip.mk
> @@ -4,7 +4,7 @@
>   #
>   ################################################################################
>   
> -GZIP_VERSION = 1.11
> +GZIP_VERSION = 1.12
>   GZIP_SOURCE = gzip-$(GZIP_VERSION).tar.xz
>   GZIP_SITE = $(BR2_GNU_MIRROR)/gzip
>   # Some other tools expect it to be in /bin
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2022-04-19 20: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 ` Arnout Vandecappelle [this message]
2022-05-22 10:30 ` [Buildroot] [PATCH 1/2] package/gzip: security bump to 1.12 Peter Korsgaard

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=087b047b-348d-cd25-8f40-4a551851c38b@mind.be \
    --to=arnout@mind.be \
    --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.