This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Vtable pointer verification, gcc changes (patch 2 of 2)

From: Caroline Tice <cmtice at google dot com>
To: Florian Weimer <fweimer at redhat dot com>
Cc: gcc-patches at gcc dot gnu dot org
Date: Thu, 8 Nov 2012 08:56:09 -0800
Subject: Re: [PATCH] Vtable pointer verification, gcc changes (patch 2 of 2)
References: <CABtf2+SdU_aWMj-v6J=WM8onenUX0UZY72bdKj2a4JEtUXe-pw@mail.gmail.com> <509B7D24.5040201@redhat.com>

Most likely use-after-free issues, but any memory use bug lays the
program open to these attacks.

-- Caroline Tice
cmtice@google.com


On Thu, Nov 8, 2012 at 1:36 AM, Florian Weimer <fweimer@redhat.com> wrote:
> On 11/05/2012 06:48 PM, Caroline Tice wrote:
>
>> As requested, I have split the original patch into two parts: GCC
>> changes and runtime library changes.  The attached patch is fore the
>> gcc changes.
>
>
> Out of curiosity, what's the primary source of wrong vtable values you
> expect?  User-after-free issues, heap spraying, or something else?
>
> --
> Florian Weimer / Red Hat Product Security Team

References:
- [PATCH] Vtable pointer verification, gcc changes (patch 2 of 2)
  - From: Caroline Tice
- Re: [PATCH] Vtable pointer verification, gcc changes (patch 2 of 2)
  - From: Florian Weimer

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]