RabbitMQ is a messaging and streaming broker
Why It Matters
Analysis dossierWhy It Matters
RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.2.9 and 4.3.3, AMQP 1.0 management exchange.declare skips alternate-exchange permission check. pUT /exchanges/:name (lines 192-240) checks only configure on the declared exchange and passes XArgs straight to rabbitexchange:declare/7. It omits the checkreadpermitted(X) + checkwritepermitted(AE) that rabbitchannel.erl:2540-2548 enforces for the alternate-exchange argument on the AMQP 0-9-1 path. The same file already implements the analogous DLX check for queues (lines 708-719), confirming this is a missing-check bug rather than intentional A user with only configure on exchange X can route X's unroutable messages into an alternate exchange they have no write permission AMQP 1.0 enabled (default in RabbitMQ 4.x) Attacker has configure on at least one exchange but lacks write on the target. This issue is fixed in versions 4.2.9 and 4.3.3.
Medium
Unknown
Unknown
Risk basis: Microsoft or Microsoft-managed product relevance; No confirmed exploitation signal in current enrichment
Affected Products & Remediation
1 source-backed product- broadcom rabbitmq server · >= 4.2.0 < 4.2.9; >= 4.3.0 < 4.3.3 · NVD CPE · Source
Vendor or catalog guidance (source)
Not provided by source
Known exploitation (source facts)
Only what a source states. Unknown means no source has said either way; it is not "not exploited".
- CISA KEV
- Unknown
- Exploited (source statement)
- Unknown
- Publicly disclosed (source)
- Unknown
Suggested hunting (rule-based inference)
SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.
Matched authorization-bypass (CWE-862)
Exposure
- Locate affected authorization controls and verify deployed versions.Telemetry: Application inventory · The source must identify the affected control. · Rule authorization-bypass
Exploitation evidence
- Review privileged operations performed by unexpected users on affected deployments.Telemetry: Application audit logs · Authorization anomalies can support a targeted hunt. · Rule authorization-bypass
Response
- Confirm the vendor mitigation and recheck access decisions.Telemetry: Application audit logs · Access testing verifies the local fix. · Rule authorization-bypass
CISA KEV Record
CISA KEV status was not determined for this record.
Change History & Source Data
— No recorded material change
- CNA / source
- security-advisories@github.com
- Record status · verification
- UPDATED · NVD API
- CPE
- cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*
Evidence & Provenance
— No published hunting query names this record. Browse community and library queries instead.
Correlated briefings
— No published briefing references this CVE