From: Derrick McKee <derrick.mckee@gmail.com>
To: kernel-hardening@lists.openwall.com
Cc: linux-hardening@vger.kernel.org
Subject: CVE Proofs of Concept
Date: Sat, 19 Mar 2022 08:10:34 -0400 [thread overview]
Message-ID: <CAJoBWHxmsWThoQXNXRfDwmT2z=iEtwPQMU1iVtTZdNmqaCCaeQ@mail.gmail.com> (raw)
Hello,
I am a Ph.D. student at Purdue University researching kernel
compartmentalization. I am currently conducting evaluation for a
follow-up paper to one published at NDSS 22 titled 'Preventing Kernel
Hacks with HAKC' (see [1]). We are interested in empirically
evaluating our compartmentalization policies by determining if targets
of exploits (which we refer to as exploit sinks) are placed in a
different compartment from code that accesses the target (which we
refer to as exploit sources).
To that end, we are looking for a set of kernel exploit proofs of
concept that we can execute and examine. I realize such a set could
be sensitive, and I will follow all safety procedures in the handling
and execution of any PoC. In lieu of a set of PoCs, are there any
statistics of kernel structures that are targeted by attackers? I
would imagine, for example, that struct cred would be heavily
targeted, but how often and what other kernel structures are targeted
would be invaluable. Thank you for any insight you might have.
[1] https://www.ndss-symposium.org/ndss2022/accepted-papers/
--
Derrick McKee
Phone: (703) 957-9362
Email: derrick.mckee@gmail.com
reply other threads:[~2022-03-19 12:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAJoBWHxmsWThoQXNXRfDwmT2z=iEtwPQMU1iVtTZdNmqaCCaeQ@mail.gmail.com' \
--to=derrick.mckee@gmail.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-hardening@vger.kernel.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).