From: Tim <tim-qemu@sentinelchicken.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] Security house-cleaning
Date: Wed, 16 Jun 2004 21:38:38 -0700 [thread overview]
Message-ID: <20040617043838.GA1938@sentinelchicken.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]
After noticing the string format vulnerability the other day, I decided
to do a quick audit of calls to commonly mis-used string functions. I
came across a few that looked a bit troublesome, in a security sense, so
I have updated them to their safer, length-checking counterparts.
I have to say, the core QEMU code is quite clean, and I feel that much
more confident in using it for honeypot projects later on. ;-) The
biggest culprit in terms of potential overflows, was the slirp code.
There were some disturbing instances where strings were being pulled
directly from the command line and tossed into a fixed-length buffer
with no checks. =-X I can't say that I understand at all how slirp
works, so I don't know if it is exploitable.
I will continue to develop this patch, as I monitor and test the newest
code on HEAD. I do not currently use many parts of the codebase in my
testing though, so be sure to test the patch well before committing it,
particularly the slirp changes.
thanks,
tim
PS - a README is included for you Hetz, if you want to place it on your
site.
[-- Attachment #2: security_20040616.tar.gz --]
[-- Type: application/octet-stream, Size: 2575 bytes --]
next reply other threads:[~2004-06-17 4:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 4:38 Tim [this message]
2004-06-17 15:07 ` [Qemu-devel] [PATCH] Security house-cleaning Gianni Tedesco
2004-06-17 15:14 ` Renzo Davoli
2004-06-17 15:24 ` Panagiotis Issaris
2004-06-17 15:27 ` Sebastien Bechet
2004-06-17 16:37 ` Tim
2004-06-17 17:03 ` Sander Nagtegaal
2004-06-17 17:16 ` Gianni Tedesco
2004-06-17 19:59 ` Renzo Davoli
2004-06-17 16:05 ` Tim
2004-06-17 17:41 ` Gianni Tedesco
2004-06-18 4:13 ` Tim
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=20040617043838.GA1938@sentinelchicken.org \
--to=tim-qemu@sentinelchicken.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).