Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Common Criteria Guide for SRX380 Devices
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Configuring IP Teardrop Attack Screen

date_range 11-May-22

This topic describes how to configure detection of an IP teardrop attack.

Teardrop attacks exploit the reassembly of fragmented IP packets. In the IP header, one of the field is the fragment offset fields, which indicates the starting position, or offset of the data contained in a fragmented packet, relative to the data of the original unfragmented packet. When the sum of the offset and size of one fragmented packet differs from that of the next fragmented packet, the packets overlap and the server attempting to reassemble the packet might crash.

To enable detection of a teardrop attack:

  1. Configure interfaces and assign IP addresses to the interfaces.
    content_copy zoom_out_map
    [edit]
    user@host# set interfaces ge-0/0/1 unit 0 family inet address 192.0.2.0/24
    user@host# set interfaces ge-0/0/3 unit 0 family inet address 198.51.100.0/24
    
  2. Configure security zones trustZone and untrustZone and assign interfaces to them.
    content_copy zoom_out_map
    [edit]
    user@host# set security zones security-zone trustZone host-inbound-traffic system-services all
    user@host# set security zones security-zone trustZone host-inbound-traffic protocols all
    user@host# set security zones security-zone trustZone interfaces ge-0/0/1.0
    user@host# set security zones security-zone untrustZone host-inbound-traffic system-services all
    user@host# set security zones security-zone untrustZone host-inbound-traffic protocols all
    user@host# set security zones security-zone untrustZone interfaces ge-0/0/3.0
    
  3. Configure security policies from untrustZone to trustZone.
    content_copy zoom_out_map
    [edit]
    user@host# set security policies from-zone untrustZone to-zone trustZone policy policy1 match source-address any
    user@host# set security policies from-zone untrustZone to-zone trustZone policy policy1 match destination-address any
    user@host# set security policies from-zone untrustZone to-zone trustZone policy policy1 match application any
    user@host# set security policies from-zone untrustZone to-zone trustZone policy policy1 then permit
    user@host# set security policies default-policy deny-all
    
  4. Configure the security screen option and attach it to the untrustZone.
    content_copy zoom_out_map
    [edit]
    user@host# set security screen ids-option untrustScreen ip tear-drop
    user@host# set security zones security-zone untrustZone screen untrustScreen
    user@host# set security screen ids-option untrustScreen alarm-without-drop
    
  5. Configure syslog.
    content_copy zoom_out_map
    [edit]
    user@host# set system syslog file syslog any any
    user@host# set system syslog file syslog archive size 10000000
    user@host# set system syslog file syslog structured-data
    user@host# set security policies from-zone untrustZone to-zone trustZone policy policy1 then log session-init
    user@host# set security policies from-zone untrustZone to-zone trustZone policy policy1 then log session-close
    
  6. Commit the configuration.
    content_copy zoom_out_map
    [edit]
    user@host# commit
    
footer-navigation