# Message broker permissions cross a virtual-host boundary

A restricted broker identity can act on a queue or exchange belonging to a different isolated fixture tenant.

**Candidate CWE:** [CWE-863](https://cwe.mitre.org/data/definitions/863.html)

## Test hypothesis

Create two owned virtual hosts with one synthetic queue each. Compare the same permitted operation in A with the disallowed operation in B; use one marked message only if publishing or consuming is part of the authorized test.

## Evidence required

Broker identity, virtual host/resource names, configured permission regexes, precise operation and marker/acknowledgement result.

## Rule out false positives

Successful broker login alone, intended shared virtual hosts, a permission pattern that correctly matches only A's resources, or a test that changes the fixture owner's account.

## Playbook and command references

- [Database, cache, queue and management service boundaries](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/modules/network-service-boundaries.html) — Move from a reachable socket to a minimal proof of unintended service authority using synthetic records and paired identities.

[Find the associated command snippets](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/commands.html?q=Database%2C%20cache%2C%20queue%20and%20management%20service%20boundaries)

## Referenced by these target playbooks

[Network services](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/network.html) · [Cloud & containers](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/cloud.html) · [OSS & self-hosted](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/oss.html)

## Report checklist

- [ ] Capture the affected version, configuration, identities, and object ownership.
- [ ] Preserve a valid baseline and a negative control.
- [ ] Reproduce the forbidden data access, action, or state change on controlled fixtures.
- [ ] Explain the intended security rule and why the observed behavior violates it.
- [ ] State prerequisites, uncertainty, cleanup, and the smallest demonstrated impact.

## Conditional ATT&CK mapping

No direct ATT&CK mapping selected. Record the weakness and demonstrated impact without forcing an adversary-behavior classification. See the [mapping guide](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/attack.html).

## Primary references

- [RabbitMQ authentication and resource permissions](https://www.rabbitmq.com/docs/access-control)

[Back to the complete vulnerability catalog](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/vulnerabilities.html)