From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: bancfc@openmailbox.org
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU soundcards vulnerable to jack retasking?
Date: Mon, 28 Nov 2016 10:19:16 +0000 [thread overview]
Message-ID: <20161128101916.GB2148@work-vm> (raw)
In-Reply-To: <290015b23a9ec5033ee65209882dcbc0@openmailbox.org>
* bancfc@openmailbox.org (bancfc@openmailbox.org) wrote:
> Recent security research shows that soundcards support surreptitiously
> switching line-out jacks into line-in by modifying the software stack. The
> way modern speakers and headphones are designed makes them readily usable as
> microphones. The Intel High Definition (HD) Audio standards which all modern
> consumer soundcards are based mandates this stupidity.
>
> https://arxiv.org/ftp/arxiv/papers/1611/1611.07350.pdf
>
> Does anyone know if QEMU's emulated sound devices follow this standard? If
> yes then a malicious guest that can modify the virt sound hardware can turn
> PC speakers into surveillance devices even if the microphone is disabled on
> the host. The only solution is completely denying untrusted VMs access to a
> virtual sound device.
I think it's reasonably isolated; the emulated audio controller ends up using
normal pulseaudio/alsa etc to talk to your host's audio system - so I don't
think it should be able to screw around with low level settings of the codecs.
Dave
>
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2016-11-28 10:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 20:25 [Qemu-devel] QEMU soundcards vulnerable to jack retasking? bancfc
2016-11-28 10:19 ` Dr. David Alan Gilbert [this message]
2016-11-28 10:38 ` Daniel P. Berrange
2016-11-28 10:30 ` Gerd Hoffmann
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=20161128101916.GB2148@work-vm \
--to=dgilbert@redhat.com \
--cc=bancfc@openmailbox.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.