# AMQP

> Message broker protocol

- **URL:** https://hackindex.io/services/amqp
- **Type:** Service
- **Default ports:** 5671, 5672
- **Tags:** amqp, messaging, broker, network, protocol
- **Published:** 2026-01-26
- **Updated:** 2026-07-13

AMQP (Advanced Message Queuing Protocol) is an open messaging protocol commonly implemented by RabbitMQ, Apache Qpid, and other message brokers. The standard AMQP port is **TCP 5672** for plaintext connections and **TCP 5671** for TLS. RabbitMQ also exposes an HTTP management UI on **TCP 15672**. Nmap identifies the service as `amqp`.

Message brokers are attractive targets because they sit between application components and often carry sensitive data such as authentication tokens, job payloads, and internal API calls. Default credentials (`guest:guest` on RabbitMQ) are a frequent finding. When access controls are weak, an attacker can subscribe to queues, publish malicious messages, or extract credentials stored in broker configurations.

Enumeration typically starts with checking the management UI for unauthenticated access, then testing default or brute-forced credentials on both AMQP and the HTTP API. From there, listing exchanges, queues, bindings, and connected consumers reveals the internal messaging architecture and potential data exposure.

## Phases

- [Enumeration](https://hackindex.io/services/amqp/enumeration.md): Fingerprint brokers, find management ports, test credentials and permission (3 guides)
- [Vulnerability Discovery](https://hackindex.io/services/amqp/vulnerability-discovery.md): Guides for testing default credentials on RabbitMQ services (1 guides)
- [Exploitation](https://hackindex.io/services/amqp/exploitation.md): Exploit RabbitMQ admin API to dump data and add backdoor users (1 guides)