RFC 1858: Security Considerations for IP Fragment Filtering

IP fragmentation can be used to disguise TCP packets from IP filters used in routers and hosts. This document describes two methods of attack as well as…

Read RFC 1858 on the RFC Editor

Outgoing relationships (1 related RFC)

Informative reference — RFC 815: IP datagram reassembly algorithms

Incoming relationships (13 related RFCs)

Updated by — RFC 3128: Protection Against a Variant of the Tiny Fragment Attack (RFC 1858)
Normatively referenced by — RFC 7588: A Widely Deployed Solution to the Generic Routing Encapsulation (GRE) Fragmentation Problem
Informatively referenced by — RFC 4960: Stream Control Transmission Protocol
Informatively referenced by — RFC 4787: Network Address Translation (NAT) Behavioral Requirements for Unicast UDP
Informatively referenced by — RFC 7597: Mapping of Address and Port with Encapsulation (MAP-E)
Informatively referenced by — RFC 9260: Stream Control Transmission Protocol
Informatively referenced by — RFC 4459: MTU and Fragmentation Issues with In-the-Network Tunneling
Informatively referenced by — RFC 4942: IPv6 Transition/Co-existence Security Considerations
Informatively referenced by — RFC 5722: Handling of Overlapping IPv6 Fragments
Informatively referenced by — RFC 8900: IP Fragmentation Considered Fragile
Informatively referenced by — RFC 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status
Informatively referenced by — RFC 4036: Management Information Base for Data Over Cable Service Interface Specification (DOCSIS) Cable Modem Termination Systems for Subscriber Management
Informatively referenced by — RFC 4639: Cable Device Management Information Base for Data-Over-Cable Service Interface Specification (DOCSIS) Compliant Cable Modems and Cable Modem Termination Systems