From: dion@linutronix.de
To: qemu-devel@nongnu.org
Cc: Olivier Dion <dion@linutronix.de>, john.ogness@linutronix.de
Subject: [Qemu-devel] [PATCH 1/1] linux-user: Handle /proc/self/exe in syscall execve
Date: Wed, 7 Aug 2019 15:54:58 +0200 [thread overview]
Message-ID: <20190807135458.32440-2-dion@linutronix.de> (raw)
In-Reply-To: <20190807135458.32440-1-dion@linutronix.de>
From: Olivier Dion <dion@linutronix.de>
If not handled, QEMU will execve itself instead of the emulated
process. This could result in potential security risk.
Signed-off-by: Olivier Dion <dion@linutronix.de>
---
linux-user/syscall.c | 13 ++++++++++++-
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 8367cb138d..1a475896a6 100644
--- a/linux-user/syscall.c
+++ b/linux-user/syscall.c
@@ -7504,7 +7504,18 @@ static abi_long do_syscall1(void *cpu_env, int num, abi_long arg1,
* before the execve completes and makes it the other
* program's problem.
*/
- ret = get_errno(safe_execve(p, argp, envp));
+ {
+ const char *pathname = p;
+ char real_path[PATH_MAX];
+ if (is_proc_myself(pathname, "exe")) {
+ if (NULL == realpath(exec_path, real_path)) {
+ ret = get_errno(-1);
+ goto execve_efault;
+ }
+ pathname = real_path;
+ }
+ ret = get_errno(safe_execve(pathname, argp, envp));
+ }
unlock_user(p, arg1, 0);
goto execve_end;
--
2.22.0
next prev parent reply other threads:[~2019-08-07 13:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 13:54 [Qemu-devel] [PATCH 0/1] Handle /proc/self/exe in execve dion
2019-08-07 13:54 ` dion [this message]
2019-08-23 16:58 ` [Qemu-devel] [PATCH 1/1] linux-user: Handle /proc/self/exe in syscall execve Laurent Vivier
2019-09-02 17:36 ` Olivier Dion
2019-09-02 19:02 ` Laurent Vivier
2019-09-16 15:55 ` [Qemu-devel] [PATCH v2 0/1] Handle /proc/self/exe in execve Olivier Dion
2019-09-16 15:55 ` [Qemu-devel] [PATCH v2 1/1] Handle /proc/self/exe in syscall execve Olivier Dion
2019-09-16 16:55 ` [Qemu-devel] [PATCH v2 0/1] Handle /proc/self/exe in execve no-reply
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=20190807135458.32440-2-dion@linutronix.de \
--to=dion@linutronix.de \
--cc=john.ogness@linutronix.de \
--cc=qemu-devel@nongnu.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).