WebRTC
— Web Real-Time CommunicationWebRTC enables sub-second latency peer-to-peer audio, video, and data communication directly between browsers and mobile devices. It leverages SDP (Session Description Protocol) for offer/answer signaling, STUN/TURN for NAT traversal, and SRTP/SCTP for encrypted media and data channels.
Interactive Session: How WebRTC Works
Step through the packet exchange sequence between nodes.
Interactive Execution Sandbox
Interact with a live or clearly-labelled simulated instance of WebRTC.
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.
ICE candidate IP leak
ReconnaissanceICE candidates can reveal local and public IP addresses to the remote peer before consent.
Collect candidates
The remote peer gathers host and server-reflexive addresses.
Candidates revealing private ranges.
Privacy loss and network reconnaissance.
Defences that matter
- Force TURN relay for sensitive calls
- Use mDNS host candidates
- Review ICE policy and permissions
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
- Peer-to-peer direct audio/video streaming via SRTP (Secure Real-time Transport Protocol)
- RTCDataChannel for bidirectional, low-latency binary and text transmission over SCTP/DTLS
- ICE (Interactive Connectivity Establishment) with STUN and TURN for NAT and firewall traversal
- Adaptive bitrate and jitter buffer management tailored for unstable mobile networks
Real-World Use Cases
- Google Meet, Discord, and Zoom browser video conferences
- Cloud gaming streaming (GeForce Now, Xbox Cloud)
- Browser-to-browser P2P file sharing
Advantages & Strengths
- Ultra-low latency (<200ms glass-to-glass)
- Encrypted by default via DTLS and SRTP
- Native browser API without third-party plugins
Limitations & Vulnerabilities
- P2P mesh topology does not scale past 4–6 participants without a Selective Forwarding Unit (SFU) media server