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
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 — Move from a reachable socket to a minimal proof of unintended service authority using synthetic records and paired identities.
Find the associated command snippets
Referenced by these target playbooks#
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.