ProtoStackv0.1

Interactive Protocol Visualizer

Cloud & MessagingProfessional trackAdvancedOSI: Application LayerDefault Port: 5672Standard: OASIS Standard / ISO/IEC 19464

AMQP

— Advanced Message Queuing Protocol

AMQP defines wire-level protocols and message broker models featuring Exchanges (Direct, Fanout, Topic, Headers), Queues, and Bindings. It guarantees enterprise-grade message delivery, transactional publishing, and distributed worker load leveling.

Read first: TCP, TLS 1.3Content reviewed 2026-11-18

Interactive Session: How AMQP Works

Step through the packet exchange sequence between nodes.

Interactive Execution Sandbox

Interact with a live or clearly-labelled simulated instance of AMQP.

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

AMQP permission bypass

Injection

Broad vhost permissions or the default guest account let a client publish to or consume from queues it should not touch.

Attackersimulated
AMQPtarget
Attack step 1 of 3
Connect to the broker

Default or reused credentials are accepted.

What a defender can see

Guest logins and new connections.

Impact if unmitigated

Job injection, data theft and workflow corruption.

Defences that matter
  • Remove the guest account
  • Per-vhost, per-user permissions
  • TLS and connection monitoring

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

  • Flexible routing via Exchanges (Direct, Fanout, Topic, Headers)
  • Reliable message acknowledgments and dead-letter exchanges (DLX)
  • Flow control, publisher confirms, and prefetch limits
  • Binary encoding format for high throughput

Real-World Use Cases

  • Asynchronous background task queues (Celery, BullMQ)
  • Financial trading order execution queues
  • Microservices event-driven choreography

Advantages & Strengths

  • Very rich routing semantics without client application code complexity
  • Strict delivery guarantees and durable message persistence

Limitations & Vulnerabilities

  • Higher broker complexity and resource overhead than lightweight MQTT or Kafka