From: Eric Dumazet <eric.dumazet@gmail.com>
To: Aristide Fattori <joystick@security.dico.unimi.it>
Cc: netdev@vger.kernel.org, roberto.paleari@emaze.net
Subject: Re: Null pointer dereference in icmp_send
Date: Mon, 16 May 2011 23:27:16 +0200 [thread overview]
Message-ID: <1305581236.9466.4.camel@edumazet-laptop> (raw)
In-Reply-To: <BANLkTi=uBDOQOJJMGn6V0Ne7OjQ7kGc-2w@mail.gmail.com>
Le lundi 16 mai 2011 à 23:06 +0200, Aristide Fattori a écrit :
> Hi everybody,
>
> in function icmp_send() (net/ipv4/icmp.c), the parameter passed to
> dev_net() function is not properly validated. This can lead to a NULL
> pointer dereference that crashes the kernel. The bug can be triggered
> remotely, by flooding the target with fragmented IPv4 packets.
> Important fields in the IP packet are:
> * Flags: the MF flag must be set.
> * Fragment ID: using pseudo-random values for this field quickly
> fills fragmented queues in the victim's kernel, as it is unable to
> easily reassemble received packets.
> * TOS: using pseudo-random values for this field triggers the
> creation of more than one route cache entry for the same destination
> address, increasing the chances of incurring in the error condition
> described before.
> Other fields of the packet do not really matter, and they can be set
> to arbitrary values.
>
> If you are interested, we can provide a small and very dirty python
> script that easily triggers the error condition.
>
Hi
You forgot to tell us which linux version you used ?
We had some fixes lately in this area.
Thanks
next prev parent reply other threads:[~2011-05-16 21:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 21:06 Null pointer dereference in icmp_send Aristide Fattori
2011-05-16 21:22 ` David Miller
2011-05-16 21:27 ` Eric Dumazet [this message]
2011-05-16 21:38 ` Eric Dumazet
2011-05-17 7:31 ` Aristide Fattori
2011-05-17 7:51 ` Eric Dumazet
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=1305581236.9466.4.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=joystick@security.dico.unimi.it \
--cc=netdev@vger.kernel.org \
--cc=roberto.paleari@emaze.net \
/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