From: Scott Gayou <sgayou@redhat.com>
To: nickc@redhat.com
Cc: ian@airs.com, gcc-patches@gcc.gnu.org, binutils@sourceware.org,
matz@gcc.gnu.org, jason@redhat.com
Subject: Re: RFA/RFC: Add stack recursion limit to libiberty's demangler
Date: Thu, 29 Nov 2018 17:08:00 -0000 [thread overview]
Message-ID: <CA+2=X7vL+4BPOGhGpJNzsFTjo2vNSaJw7QTMdJLS_pMNZKX0qg@mail.gmail.com> (raw)
In-Reply-To: <87sgzkszbh.fsf@redhat.com>
Thank you for looking into this Nick. I've been staring at a few of these
CVEs off-and-on for a few days, and the following CVEs all look like
duplicates:
CVE-2018-17985: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87335
CVE-2018-18484: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87636
CVE-2018-18701: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87675
CVE-2018-18700: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87681
There may be more. I think Mitre is scanning the gnu bugzilla and assigning
CVEs? This does look like a legitimate very low criticality "denial of
service", but generating new CVEs for every unique poc file against the
same root cause doesn't seem useful. Perhaps some of these should be
rejected?
--
Scott Gayou / Red Had Product Security
next prev parent reply other threads:[~2018-11-29 17:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 15:01 Nick Clifton
2018-11-29 17:08 ` Scott Gayou [this message]
2018-11-30 8:42 ` Nick Clifton
2018-11-29 18:20 ` Pedro Alves
2018-11-29 22:18 ` Ian Lance Taylor
[not found] ` <87h8fza6fh.fsf@tromey.com>
[not found] ` <43e6c9e6-8249-bf56-aed8-90d0f771c567@redhat.com>
2018-11-30 11:58 ` Pedro Alves
2018-11-30 8:38 Nick Clifton
2018-11-30 8:42 ` Jakub Jelinek
2018-11-30 10:27 ` Nick Clifton
2018-11-30 13:46 ` Michael Matz
2018-11-30 14:57 ` Ian Lance Taylor
2018-12-02 0:49 ` Cary Coutant
2018-12-03 14:53 ` Nick Clifton
2018-12-03 22:00 ` Joseph Myers
2018-11-30 13:56 ` Ian Lance Taylor
2018-11-30 14:03 ` Jakub Jelinek
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='CA+2=X7vL+4BPOGhGpJNzsFTjo2vNSaJw7QTMdJLS_pMNZKX0qg@mail.gmail.com' \
--to=sgayou@redhat.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=ian@airs.com \
--cc=jason@redhat.com \
--cc=matz@gcc.gnu.org \
--cc=nickc@redhat.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).