From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References:

In-Reply-To: From: Carter Cheng Date: Fri, 22 Feb 2019 00:20:19 +0800 Message-ID: Subject: Re: classes of methods for gaining access to kernel memory Content-Type: multipart/alternative; boundary="0000000000006673d2058269da97" To: Kees Cook Cc: Kernel Hardening List-ID: --0000000000006673d2058269da97 Content-Type: text/plain; charset="UTF-8" I was looking over some recent papers for Usenix Security and there are a couple on data oriented programming and I have been wondering if there are known mitigation techniques for this kind of data corruption attack or other attacks that don't involve control flow hijacking. On Thu, Feb 21, 2019 at 9:17 AM Kees Cook wrote: > On Sun, Feb 10, 2019 at 3:13 AM Carter Cheng > wrote: > > I was reading a paper on kernel data attacks and the paper mentions > methods for gaining control of kernel memory beyond overflow type attacks. > This would seem to suggest that methods exist for this in certain cases > beyond what can be caught by spatial safety checks. Are there general > classes of such methods that one needs to be aware of? And what are they? > > If I follow what you're asking, I'd think race conditions would be an > example of another major class of attacks against the kernel. For > example, look at the DirtyCOW attack: that was a race condition > against the kernel's VFS that wouldn't get caught by bounds checking, > etc, etc. > > -- > Kees Cook > --0000000000006673d2058269da97 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

I was looking over some recent papers for Usenix Security = and there are a couple on data oriented programming and I have been wonderi= ng if there are known mitigation techniques for this kind of data corruptio= n attack or other attacks that don't involve control flow hijacking.=C2= =A0

On Thu, Feb 21, 2019 at 9:17 AM Kees Cook <keescook@chromium.org> wrote:

On Sun, Feb 10, 2019 at 3:13 AM Carter = Cheng <carter= cheng@gmail.com> wrote:
> I was reading a paper on kernel data attacks and the paper mentions me= thods for gaining control of kernel memory beyond overflow type attacks. Th= is would seem to suggest that methods exist for this in certain cases beyon= d what can be caught by spatial safety checks. Are there general classes of= such methods that one needs to be aware of? And what are they?

If I follow what you're asking, I'd think race conditions would be = an
example of another major class of attacks against the kernel. For
example, look at the DirtyCOW attack: that was a race condition
against the kernel's VFS that wouldn't get caught by bounds checkin= g,
etc, etc.

--
Kees Cook

--0000000000006673d2058269da97--