public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29467] CVE-2018-25032 : Memory corruption when deflating if the input has many distant matches
Date: Tue, 22 Nov 2022 14:21:43 +0000	[thread overview]
Message-ID: <bug-29467-4717-2FncENopRS@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29467-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29467

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nickc at redhat dot com,
                   |                            |vries at gcc dot gnu.org

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Gino K Sebastian from comment #1)
> Do we have any update on this CVE?
> Is it still open?

We have:
...
commit 8e6b35366073a1a71df805061ecf016cc915a9f9
Author: Nick Clifton <nickc@redhat.com>
Date:   Tue Apr 12 16:24:10 2022 +0100

    Rebase the zlib sources to the 1.2.12 release
...
so AFAIU the CVE should be fixed in the next release (13.1).

I suppose the problem still exists on 12.1, the version on which this was
reported.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-11-22 14:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-10 14:18 [Bug gdb/29467] New: " vishnu.sarath at ashling dot com
2022-08-10 14:20 ` [Bug gdb/29467] " vishnu.sarath at ashling dot com
2022-11-22 13:07 ` ginoks at gmail dot com
2022-11-22 14:21 ` vries at gcc dot gnu.org [this message]
2022-11-22 14:22 ` vries at gcc dot gnu.org
2022-11-22 17:41 ` tromey at sourceware dot org

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=bug-29467-4717-2FncENopRS@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).