From: Jeff Law <jeffreyalaw@gmail.com>
To: "Luís Ferreira" <contact@lsferreira.net>,
ibuclaw@gdcproject.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libiberty: prevent buffer overflow when decoding user input
Date: Tue, 5 Oct 2021 09:00:26 -0600 [thread overview]
Message-ID: <91b18e07-1aac-f576-f9eb-7a152adbf737@gmail.com> (raw)
In-Reply-To: <09fab85115a5c1e683400afd646c93369ba171c5.camel@lsferreira.net>
On 10/4/2021 10:52 AM, Luís Ferreira wrote:
> On Thu, 2021-09-23 at 09:50 -0600, Jeff Law wrote:
>>
>> On 9/23/2021 4:16 AM, ibuclaw--- via Gcc-patches wrote:
>>>> On 22/09/2021 03:10 Luís Ferreira <contact@lsferreira.net> wrote:
>>>>
>>>>
>>>> Currently a stack/heap overflow may happen if a crafted mangle is
>>>> maliciously used to cause denial of service, such as intentional
>>>> crashes
>>>> by accessing a reserved memory space.
>>>>
>>> Hi,
>>>
>>> Thanks for this. Is there a test that could trigger this code
>>> path?
>> I don't think Luis has commit privs, so I went ahead and committed
>> this
>> patch.
>>
>> Yea, a testcase would be great.
>>
>> Jeff
>>
> Does the test suite runned against address sanitization? if yes, I can
> submit a patch to make this fail, otherwise it is hard to trigger a
> consistent crash for this issue.
Unfortunately, no it doesn't run with sanitization. If it's too painful
to create a test, don't worry about it. It happens from time to time.
jeff
next prev parent reply other threads:[~2021-10-05 15:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 1:10 Luís Ferreira
2021-09-23 10:16 ` ibuclaw
2021-09-23 15:40 ` Luís Ferreira
2021-09-23 15:50 ` Jeff Law
2021-10-04 16:52 ` Luís Ferreira
2021-10-05 15:00 ` Jeff Law [this message]
2021-10-05 17:26 ` Luís Ferreira
2021-10-06 1:49 ` Eric Gallager
2021-10-07 18:29 ` Luís Ferreira
2021-10-08 16:52 ` Iain Buclaw
2021-10-08 17:08 ` Luís Ferreira
2021-10-08 20:11 ` Iain Buclaw
2021-10-12 12:54 ` Luís Ferreira
2021-10-12 19:40 ` Eric Gallager
2021-10-12 20:25 ` Luís Ferreira
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=91b18e07-1aac-f576-f9eb-7a152adbf737@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=contact@lsferreira.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=ibuclaw@gdcproject.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).