From: Sandra Loosemore <sandra@codesourcery.com>
To: Simon Marchi <simon.marchi@polymtl.ca>,
Kevin Buettner <kevinb@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [patch] Fix CVE-2017-9778
Date: Thu, 25 Apr 2019 14:34:00 -0000 [thread overview]
Message-ID: <c343ca61-003b-bf2b-a9cb-8f1a54eb5a43@codesourcery.com> (raw)
In-Reply-To: <7662d84ed430765775cfb3750a155ba4@polymtl.ca>
On 4/24/19 9:25 PM, Simon Marchi wrote:
> On 2019-04-24 20:56, Kevin Buettner wrote:
>> On Wed, 24 Apr 2019 10:27:39 -0600
>> Sandra Loosemore <sandra@codesourcery.com> wrote:
>>
>>> Â Â Â GDB was failing to catch cases where a corrupt ELF or core file
>>> Â Â Â contained an invalid length value in a Dwarf debug frame FDE header.
>>> Â Â Â It was checking for buffer overflow but not cases where the
>>> length was
>>> Â Â Â negative or caused pointer wrap-around.
>>>
>>> Â Â Â In addition to the additional validity check, this patch cleans
>>> up the
>>> Â Â Â multiple signed/unsigned conversions on the length field so that an
>>> Â Â Â unsigned representation is used consistently throughout.
>>>
>>>    2019-04-24 Sandra Loosemore <sandra@codesourcery.com>
>>> Â Â Â Â Â Â Â Â Â Â Â Kang Li <kanglictf@gmail.com>
>>>
>>> Â Â Â Â Â Â Â PR gdb/21600
>>>
>>> Â Â Â Â Â Â Â * dwarf2-frame.c (read_initial_length): Be consistent about
>>> using
>>> Â Â Â Â Â Â Â unsigned representation of length.
>>>        (decode_frame_entry_1): Likewise. Check for wraparound of
>>> Â Â Â Â Â Â Â end pointer as well as buffer overflow.
>>
>> This is okay.
>>
>> Kevin
>
> I would just suggest using a more descriptive commit title, stating what
> the commit actually changes in the code. It's still good to reference
> the CVE number, but by itself is not very descriptive.
Done. I pushed it as "Detect invalid length field in debug frame FDE
header."
-Sandra
next prev parent reply other threads:[~2019-04-25 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 16:27 Sandra Loosemore
2019-04-25 0:56 ` Kevin Buettner
2019-04-25 3:26 ` Simon Marchi
2019-04-25 14:34 ` Sandra Loosemore [this message]
2019-04-25 15:53 ` Kevin Buettner
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=c343ca61-003b-bf2b-a9cb-8f1a54eb5a43@codesourcery.com \
--to=sandra@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=simon.marchi@polymtl.ca \
/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