Broadcom RabbitMQ Server

RabbitMQ: Stored HTML Injection in RabbitMQ Management OAuth Error Handling

RabbitMQ arbitrary code execution using local binary planting

RabbitMQ Node can log Basic Auth header from an HTTP request

RabbitMQ: Atom exhaustion: OAuth2 JWT tag: scope values

RabbitMQ: Authenticated RabbitMQ JMS Topic Selector Users Can Consume Broker CPU with an Unbounded LIKE Regular Expression

RabbitMQ: Atom table exhaustion via stream `chunk_selector`

RabbitMQ: Atom table exhaustion via management API node field

RabbitMQ: Stream protocol skips per vhost per user connection limits

RabbitMQ: AMQP 1.0 management exchange.declare skips alternate-exchange permission check

RabbitMQ: ReDoS via management API ?name= filter

RabbitMQ: Super-stream HTTP creation skips configure-permission check

RabbitMQ: ReDoS via AMQP 1.0 SQL filter LIKE wildcard

RabbitMQ: AMQP 0-9-1 in combination with OAuth 2: consumer persistence can lead to post-revocation message disclosure

RabbitMQ: Federation and Shovel Gen-Servers Lack format_status Callback — Plaintext Credentials Exposed in Crash Dumps and sys:get_status

RabbitMQ: Cross-vhost quorum-queue status and stream tracking disclosure

RabbitMQ: list_to_atom on auth_mechanism URI tokens in amqp_client

RabbitMQ: JMS topic exchange erl_scan atom exhaustion

RabbitMQ: Consistent-hash exchange unbounded weight

RabbitMQ OAuth credential refresh retains revoked runtime tags

RabbitMQ: OAuth2 is_integer(Exp) guard skips token-expiry checks for float exp

RabbitMQ: AMQP 1.0 management `GET /bindings` exposes full binding topology to any authenticated AMQP user without resource/management permission checks

An issue was discovered in these Pivotal RabbitMQ versions: all 3.4.x versions, all 3.5.x versions, and 3.6.x versions prior to 3.6.9; and these RabbitMQ for PCF versions: all 1.5.x versions, 1.6.x versions prior to 1.6.18, and 1.7.x versions prior to 1.7.15. Several forms in the RabbitMQ management UI are vulnerable to XSS attacks.

An issue was discovered in these Pivotal RabbitMQ versions: all 3.4.x versions, all 3.5.x versions, and 3.6.x versions prior to 3.6.9; and these RabbitMQ for PCF versions: all 1.5.x versions, 1.6.x versions prior to 1.6.18, and 1.7.x versions prior to 1.7.15. Several forms in the RabbitMQ management UI are vulnerable to XSS attacks.

RabbitMQ: Shovel Management Atom Exhaustion Allows Persistent Broker-Wide Denial of Service

RabbitMQ: Atom exhaustion: to_atom on global-parameter :name

RabbitMQ: Super-stream partitions unbounded allocation

RabbitMQ: AMQP 1.0 shovel status exposes plaintext URI passwords

RabbitMQ: Stored XSS federation management plugin via unsanitized consumer_tag rendering

RabbitMQ: Unsanitized vhost names allow for XSS in management UI

RabbitMQ: Shovel DEBUG log of full state exposes decrypted URIs

RabbitMQ: protected tag bypass via bulk-delete

RabbitMQ: Monitoring-tag user can restart federation links

RabbitMQ: Passive queue/exchange declaration bypasses authorization checks, leaking queue metadata to unprivileged users

CRLF injection vulnerability in the management plugin in RabbitMQ 2.1.0 through 3.4.x before 3.4.1 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via the download parameter to api/definitions.

RabbitMQ: Admin path-traversal write via trace name

RabbitMQ XSS attack via federation and shovel endpoints

Cross-site scripting (XSS) vulnerability in the management plugin in RabbitMQ 2.1.0 through 3.4.x before 3.4.1 allows remote attackers to inject arbitrary web script or HTML via the path info to api/, which is not properly handled in an error message.

RabbitMQ: Non-RFC-conformant cookie name when clearing the auth-mechanism preference

RabbitMQ: Monitoring-tag DELETE of auth-attempt metrics