Re: IPv4 fragmentation --> The Rose Attack

From: Crist J. Clark (cristjc_at_comcast.net)
Date: 04/01/04

  • Next message: please_reply_to_security_at_sco.com: "OpenLinux: vim arbitrary commands execution through modelines" 
    Date: Wed, 31 Mar 2004 15:42:33 -0800
To: stanislav shalunov <shalunov@internet2.edu>

    On Wed, Mar 31, 2004 at 03:07:31PM -0500, stanislav shalunov wrote:
    > <gandalf@digital.net> writes:
    >
    > > While this discussion pertains to IPv4, IPv6 also allows fragmentation and I
    > > suspect IPv6 will also be affected by this attack.
    >
    > IPv6 does not have en-route fragmentation and, therefore, has no
    > reassembly. IPv6 is not affected.

    IPv6 does have end-station fragmentation, and therefore, it DOES have
    reassebly, see Section 4.5 of RFC2460. I do not see why an IPv6
    implementation would not also potentially be affected.

    This is YANFA, Yet Another IP Fragmentation Attack. Teardrop, Ping O'
    Death, NewTear, Boink, yada-yada. Some have exploited bugs in
    reassembly code (over lapping frags, >65535-byte packets, etc.) and
    others, like this, are flat out resource exhaustion DoSes.

    The IP stack needs to be sane about how many datagrams it will try to
    reassemble at once. This attack points out that when considering that,
    you need to account for the fact a malicious attacker might eat
    reassembly resources much faster than his bandwidth would seem to
    indicate (two small packets can look like almost 65535). The other
    approach is for the reassembly algorithm has to be careful about how
    it allocates buffers for reassembly. 

    -- 
Crist J. Clark                     |     cjclark@alum.mit.edu
                                   |     cjclark@jhu.edu
http://people.freebsd.org/~cjc/    |     cjc@freebsd.org
  • Next message: please_reply_to_security_at_sco.com: "OpenLinux: vim arbitrary commands execution through modelines"

    Relevant Pages

    • Re: IPv4 fragmentation --> The Rose Attack
      ... IPv6 does not have en-route fragmentation and, therefore, has no ... Interesting attack. ... cause a TCP stack to use all memory that is available to it. ...
      (Bugtraq)
    • Re: Tektronix manuals
      ... understand the fragmentation (the segments are not threaded but merely ... posted as separate messages) and reassemble them automatically? ... No reading, no saving needed. ... reassemble multi-parters from out of order fragments etc. ...
      (sci.electronics.repair)
    • Re: pf misfeature
      ... The problem is the lack of IP reassembly in this configuration. ... fragmentation occurs, ... scrub in on $if all fragment reassemble ... r = TAILQ_NEXT(r, entries); ...
      (freebsd-net)
    • Re: pf misfeature
      ... The problem is the lack of IP reassembly in this configuration. ... stateful filtering _requires_ IP reassembly. ... fragmentation occurs, ... scrub in on $if all fragment reassemble ...
      (freebsd-net)
    • Quantcast