public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@arm.com>
To: binutils@sourceware.org,
	"gdb@sourceware.org" <gdb@sourceware.org>,
	gcc@gcc.gnu.org
Subject: [CVE] zlib (< 1.2.12) memory corruption
Date: Tue, 5 Apr 2022 14:56:13 +0100	[thread overview]
Message-ID: <aeecafc4-da37-240f-8f3e-ca2ca58f364f@arm.com> (raw)

Hi,

There is a CVE [1] for zlib < 1.2.12 (released march 27th).

GCC currently uses zlib 1.2.11, and binutils-gdb imports the zlib 
directory from GCC. The recommendation is to get it updated to 1.2.12, 
which contains the proper fix [2].

It might not affect gcc/binutils/gdb since the code doesn't seem to be 
using the problematic option Z_FIXED, but it seems like a good idea to 
consider bumping the version of zlib we use.

[1] https://nvd.nist.gov/vuln/detail/CVE-2018-25032
[2] 
https://github.com/madler/zlib/commit/5c44459c3b28a9bd3283aaceab7c615f8020c531

             reply	other threads:[~2022-04-05 13:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-05 13:56 Luis Machado [this message]
2022-04-08 13:36 ` Nick Clifton
2022-04-12  7:30   ` Luis Machado
2022-04-12 15:27 ` Nick Clifton

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=aeecafc4-da37-240f-8f3e-ca2ca58f364f@arm.com \
    --to=luis.machado@arm.com \
    --cc=binutils@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sourceware.org \
    /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).