From: bancfc@openmailbox.org
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] QEMU soundcards vulnerable to jack retasking?
Date: Fri, 25 Nov 2016 21:25:00 +0100 [thread overview]
Message-ID: <290015b23a9ec5033ee65209882dcbc0@openmailbox.org> (raw)
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.
next reply other threads:[~2016-11-25 20:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 20:25 bancfc [this message]
2016-11-28 10:19 ` [Qemu-devel] QEMU soundcards vulnerable to jack retasking? Dr. David Alan Gilbert
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=290015b23a9ec5033ee65209882dcbc0@openmailbox.org \
--to=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 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).