Описание
Super-stream HTTP creation skips configure-permission check
Origin
This vulnerability was identified by Team RabbitMQ and/or other teams at Broadcom, not via a responsible disclosure from an external researcher.
Source references
deps/rabbitmq_stream_management/src/rabbit_stream_super_stream_mgmt.erl:56 · Missing Authorization
Impact
A user with management tag and vhost access — but no configure permission on any resource — can create super-streams (an exchange + N partition stream queues + bindings) via the HTTP API. The native stream-protocol path enforces configure on each resource; the HTTP path does not, creating a privilege escalation from 'can view' to 'can create persistent cluster-wide resources.'
Description
accept_content/2 at line 56 calls rabbit_stream_manager:create_super_stream/... directly after is_authorized (which only checks the management tag + vhost access via is_authorized_vhost). The stream-protocol equivalent (rabbit_stream_reader.erl create_super_stream handler) calls rabbit_stream_utils:check_super_stream_management_permitted/4 which enforces configure on the exchange and each partition queue. The HTTP handler omits this call entirely.
Exploit scenario
User 'viewer' has management tag, vhost '/' access, permissions configure='^$' write='^$' read='^$'. curl -u viewer:pw -XPUT broker:15672/api/stream/super-streams/%2F/spam -d '{"partitions":100}'. 100 stream queues + 1 exchange + 100 bindings are created and replicated cluster-wide.
Preconditions
- rabbitmq_stream_management plugin enabled
- management tag + vhost access (no resource permissions needed)
CVSS
CVSS v4.0: CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N (2.1, Low). Fixed in 4.0.22, 4.1.11, 4.2.6, 4.3.0.
Пакеты
rabbitmq
>= 4.0.0, < 4.0.22
4.0.22
rabbitmq
>= 4.1.0, < 4.1.11
4.1.11
rabbitmq
>= 4.2.0, < 4.2.6
4.2.6