From: Kees Cook <keescook@chromium.org>
To: Carter Cheng <cartercheng@gmail.com>
Cc: Kernel Hardening <kernel-hardening@lists.openwall.com>
Subject: Re: classes of methods for gaining access to kernel memory
Date: Thu, 21 Feb 2019 09:15:54 -0800 [thread overview]
Message-ID: <CAGXu5jJ11jw=RZ1X_KT7+9f_vjrvEpjADxdqedKLxSQjreG8Tw@mail.gmail.com> (raw)
In-Reply-To: <CALS6=qXN_UxEYV-6kG9_r6kv5joYdVpKU6xOhxLsPAkshzN80g@mail.gmail.com>
On Thu, Feb 21, 2019 at 8:20 AM Carter Cheng <cartercheng@gmail.com> wrote:
> 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.
Can you share some URLs and/or examples? I'm sure other folks here
would be interested to read those too.
--
Kees Cook
next prev parent reply other threads:[~2019-02-21 17:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-10 11:12 classes of methods for gaining access to kernel memory Carter Cheng
2019-02-21 1:17 ` Kees Cook
2019-02-21 16:20 ` Carter Cheng
2019-02-21 17:15 ` Kees Cook [this message]
2019-02-21 19:36 ` Carter Cheng
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='CAGXu5jJ11jw=RZ1X_KT7+9f_vjrvEpjADxdqedKLxSQjreG8Tw@mail.gmail.com' \
--to=keescook@chromium.org \
--cc=cartercheng@gmail.com \
--cc=kernel-hardening@lists.openwall.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 NNTP newsgroup(s).