From: Olivier Dion <olivier.dion@polymtl.ca>
To: Laurent Vivier <laurent@vivier.eu>
Cc: qemu-devel@nongnu.org, john.ogness@linutronix.de
Subject: Re: [Qemu-devel] [PATCH 1/1] linux-user: Handle /proc/self/exe in syscall execve
Date: Mon, 02 Sep 2019 13:36:56 -0400 [thread overview]
Message-ID: <875zmaeh1j.fsf@polymtl.ca> (raw)
In-Reply-To: <7a8fa9b4-01b5-e431-be89-00e73235e3ff@vivier.eu>
On 2019-08-23T12:58:43-0400, Laurent Vivier <laurent@vivier.eu> wrote:
> Le 07/08/2019 à 15:54, dion@linutronix.de a écrit :
> > 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.
> >
> Could you explain what you mean by potential security risk?
I don't have any exploit in mind, but someone motivated enough could
certainly find one. For example, it's possible to ask qemu static to
execute another program.
The main point is that an emulator should never leak informations to its
environnement. If the emulated program can determine that it is being
emulated, other than by an "official" way, then the emulator is at
fault.
--
Olivier Dion
Polymtl
next prev parent reply other threads:[~2019-09-02 17:57 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 ` [Qemu-devel] [PATCH 1/1] linux-user: Handle /proc/self/exe in syscall execve dion
2019-08-23 16:58 ` Laurent Vivier
2019-09-02 17:36 ` Olivier Dion [this message]
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=875zmaeh1j.fsf@polymtl.ca \
--to=olivier.dion@polymtl.ca \
--cc=john.ogness@linutronix.de \
--cc=laurent@vivier.eu \
--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).