SCTP
— Stream Control Transmission ProtocolSCTP combines the message-oriented nature of UDP with the reliability and congestion control of TCP. Crucially, it introduces native multi-homing (binding a connection to multiple IP addresses) and multi-streaming. It is heavily utilized in cellular 4G/5G signaling (Diameter) and WebRTC data channels.
Interactive Session: How SCTP Works
Step through the packet exchange sequence between nodes.
Interactive Execution Sandbox
Interact with a live or clearly-labelled simulated instance of SCTP.
Threat Model & Attack Simulation
How this protocol is attacked in practice, what defenders can see, and which control stops it.
Threat model & attack simulation
SimulatedDefensive education. Every step runs in this page; no traffic is generated or sent.
INIT flood
Denial of serviceA flood of spoofed INIT chunks consumes bandwidth and association table resources.
Send INIT chunks
The attacker floods INITs, often with forged source addresses.
High INIT rate and association table growth.
Service degradation despite the cookie defence.
Defences that matter
- Rate limit INIT chunks at the edge
- Firewall SCTP to known peers
- Monitor association table pressure
This is a conceptual model for defenders, not an exploit toolkit. It contains no payloads, tooling or instructions for attacking systems you do not own.
Protocol Specification & Architecture
Key characteristics, real-world deployment patterns, and trade-offs.
Core Technical Features
- Native multi-homing for high-availability carrier failover
- Multi-streaming without Head-of-Line blocking
- 4-Way handshake with Cookie mechanism preventing SYN flood attacks
- Message-oriented framing preserving application message boundaries
Real-World Use Cases
- Telecom SS7 & 4G/5G mobile core signaling
- WebRTC Data Channels
- Mission-critical air traffic control systems
Advantages & Strengths
- Immune to SYN flood attacks due to signed cookie handshake
- Fault tolerance across redundant IP links
Limitations & Vulnerabilities
- Limited native OS stack support and poor NAT middlebox traversal