qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Samuel Thibault <samuel.thibault@gnu.org>,
	slirp@lists.freedesktop.org, Petr Matousek <pmatouse@redhat.com>,
	Vishnu Dev TJ <vishnudevtj@gmail.com>,
	qemu-stable@nongnu.org, qemu-devel@nongnu.org,
	Prasad J Pandit <ppandit@redhat.com>
Subject: Re: [Qemu-devel] [Slirp] [PATCH 1/2] Do not reassemble fragments pointing outside of the original payload
Date: Thu, 29 Aug 2019 17:53:01 +0200	[thread overview]
Message-ID: <f7ce663c-0235-3585-f324-9bc74bc3b383@redhat.com> (raw)
In-Reply-To: <a032c557-7f1e-c710-f25a-e42200f0cf91@redhat.com>

On 8/29/19 5:43 PM, Philippe Mathieu-Daudé wrote:
> On 8/26/19 12:54 AM, Samuel Thibault wrote:
>> Philippe Mathieu-Daudé, le ven. 23 août 2019 17:15:32 +0200, a ecrit:
>>>> Did you make your test with commit 126c04acbabd ("Fix heap overflow in
>>>> ip_reass on big packet input") applied?
>>>
>>> Yes, unfortunately it doesn't fix the issue.
>>
>> Ok.
>>
>> Could you try the attached patch?  There was a use-after-free.  Without
>> it, I can indeed crash qemu with the given exploit.  With it I don't
>> seem to be able to crash it (trying in a loop for several minutes).
[...]
> 
> Note 2: We miss some Makefile rules in QEMU with the libslirp split.
> 
> Checkouting branches in the slirp/ directory doesn't trigger recompiling
> the slirp object, and even if I force the creation of the libslirp.a
> archive, the QEMU binaries are not linked again with the refreshed archive.

And I hit the same issue after applying your patch =)

So, using a clean workspace, I can not reproduce the null deref anymore.

If you send a proper patch, feel free to add:

Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>

Thanks!

Phil.


  reply	other threads:[~2019-08-29 15:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-22 14:41 [Qemu-devel] [PATCH 0/2] slirp: Fix heap buffer overflow during packet reassembly (CVE-2019-14378) Philippe Mathieu-Daudé
2019-08-22 14:41 ` [Qemu-devel] [PATCH 1/2] Do not reassemble fragments pointing outside of the original payload Philippe Mathieu-Daudé
2019-08-22 18:33   ` [Qemu-devel] [Slirp] " Samuel Thibault
2019-08-23 15:15     ` Philippe Mathieu-Daudé
2019-08-25 22:54       ` Samuel Thibault
2019-08-29 11:13         ` P J P
2019-08-29 15:43         ` Philippe Mathieu-Daudé
2019-08-29 15:53           ` Philippe Mathieu-Daudé [this message]
2019-08-29 16:00             ` Philippe Mathieu-Daudé
2019-08-22 14:41 ` [Qemu-devel] [RFC PATCH 2/2] Delay crash when mbufs are corrupted Philippe Mathieu-Daudé

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=f7ce663c-0235-3585-f324-9bc74bc3b383@redhat.com \
    --to=philmd@redhat.com \
    --cc=pmatouse@redhat.com \
    --cc=ppandit@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=samuel.thibault@gnu.org \
    --cc=slirp@lists.freedesktop.org \
    --cc=vishnudevtj@gmail.com \
    /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).