From: Mimi Zohar <zohar@linux.ibm.com>
To: Igor Zhbanov <i.zhbanov@omprussia.ru>, linux-integrity@vger.kernel.org
Subject: Re: Should mprotect(..., PROT_EXEC) be checked by IMA?
Date: Mon, 18 Mar 2019 17:48:35 -0400 [thread overview]
Message-ID: <1552945715.8658.299.camel@linux.ibm.com> (raw)
In-Reply-To: <cce2c4c7-5333-41c3-aeef-34d43e63acb0@omprussia.ru>
On Mon, 2019-03-18 at 18:18 +0300, Igor Zhbanov wrote:
> Hello!
>
> I've found that IMA checks for executable mmap()s but not for the combination
> of mmap(..., PROT_READ, ...) + mprotect(..., PROT_EXEC).
>
> So it looks like is possible to load arbitrary executable code by rewriting
> dlopen() and dlsym() functions to map all ELF segments read-only first then
> making them executable with mprotect().
>
> So should security_file_mprotect() be changed similarly
> to security_mmap_file() to call IMA security hook?
How? security_mmap_file() is passed a file descriptor and the
signature, stored as an xattr, can be verified.
Mimi
next prev parent reply other threads:[~2019-03-18 21:48 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 15:18 Should mprotect(..., PROT_EXEC) be checked by IMA? Igor Zhbanov
2019-03-18 21:48 ` Mimi Zohar [this message]
2019-03-19 7:50 ` Igor Zhbanov
2019-03-19 11:22 ` Mimi Zohar
2019-03-19 12:19 ` Igor Zhbanov
2019-03-19 17:05 ` Mimi Zohar
2019-03-20 8:11 ` Igor Zhbanov
2019-03-20 17:23 ` Matthew Garrett
2019-03-20 18:08 ` Igor Zhbanov
2019-03-21 11:21 ` Mimi Zohar
2019-03-21 11:48 ` Igor Zhbanov
2019-03-21 18:04 ` Matthew Garrett
2019-03-22 7:59 ` Igor Zhbanov
2019-03-28 17:17 ` Mimi Zohar
2019-03-29 10:00 ` Igor Zhbanov
2019-03-29 10:59 ` Mimi Zohar
2019-03-29 11:51 ` Jordan Glover
2019-03-29 12:28 ` Stephen Smalley
2019-03-29 12:50 ` Igor Zhbanov
2019-04-02 22:31 ` Matthew Garrett
2019-04-03 9:59 ` Igor Zhbanov
2019-04-03 16:58 ` Matthew Garrett
2019-04-03 17:31 ` Igor Zhbanov
2019-04-03 18:19 ` Matthew Garrett
2019-04-03 18:47 ` Igor Zhbanov
2019-04-03 19:25 ` Matthew Garrett
2019-04-04 11:44 ` Igor Zhbanov
2019-04-03 12:11 ` Mimi Zohar
2019-04-03 13:18 ` Perez Yves-Alexis
2019-04-03 11:57 ` Mimi Zohar
2019-04-03 13:10 ` Stephen Smalley
2019-04-03 14:33 ` Mimi Zohar
2019-04-03 14:33 ` Stephen Smalley
2019-04-03 16:21 ` Mimi Zohar
2019-03-21 18:13 ` Matthew Garrett
2019-03-19 17:07 ` Matthew Garrett
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=1552945715.8658.299.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=i.zhbanov@omprussia.ru \
--cc=linux-integrity@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 NNTP newsgroup(s).