STOMP
— Simple Text Oriented Messaging ProtocolSTOMP provides an interoperable wire format that enables web browsers (via WebSockets) and multi-language clients to communicate with enterprise message brokers (ActiveMQ, RabbitMQ, HornetQ) using simple HTTP-like headers and verbs (CONNECT, SUBSCRIBE, SEND, MESSAGE).
Interactive Session: How STOMP Works
Step through the packet exchange sequence between nodes.
Interactive Execution Sandbox
Interact with a live or clearly-labelled simulated instance of STOMP.
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.
STOMP header injection
InjectionUnsanitised CRLF sequences in STOMP headers can create extra headers or split frames.
Supply header input
User-controlled text reaches a STOMP header value.
Headers containing line breaks.
Message redirection and broker policy bypass.
Defences that matter
- Reject CRLF in header values
- Authenticate and authorise destinations
- TLS for broker connections
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
- HTTP-like header syntax (COMMAND followed by Key:Value headers and NULL byte terminator 0x00)
- Native WebSocket integration for browser-to-broker pub/sub (SockJS + STOMP.js)
- Heartbeating mechanism to detect broken connections
- Transaction support via BEGIN, COMMIT, and ABORT commands
Real-World Use Cases
- Spring Boot WebSocket real-time web applications
- Browser push notifications from enterprise JMS brokers
- Cross-language message bus abstraction between Python and Java
Advantages & Strengths
- Extremely simple and readable; easy to debug with network sniffers
- Supported out of the box in Spring Framework and enterprise brokers
Limitations & Vulnerabilities
- Text header framing introduces more byte overhead than compact binary protocols like MQTT