ProtoStackv0.1

Interactive Protocol Visualizer

Cloud & MessagingProfessional trackIntermediateOSI: Application LayerDefault Port: 61613 / WebSocketStandard: STOMP 1.2 Specification

STOMP

— Simple Text Oriented Messaging Protocol

STOMP 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).

Read first: TCPContent reviewed 2026-11-18

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

Simulated

Defensive education. Every step runs in this page; no traffic is generated or sent.

Attack library

STOMP header injection

Injection

Unsanitised CRLF sequences in STOMP headers can create extra headers or split frames.

Attackersimulated
STOMPtarget
Attack step 1 of 3
Supply header input

User-controlled text reaches a STOMP header value.

What a defender can see

Headers containing line breaks.

Impact if unmitigated

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