RabbitMQ is a messaging and streaming broker. Prior to 4.2.6, RabbitMQ AMQP 0-9-1 allows an existing consumer to keep receiving messages after OAuth token expiry or connection.update_secret refresh to reduced scopes because existing consumers are not canceled or reauthorized at delivery time after the channel user state changes. This issue is fixed in version 4.2.6.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
Present
Additional conditions required
Privileges Required
Low
Basic privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
None
No data leak
Integrity
None
No data modification
Availability
None
No disruption
CVSS Vector v4.0
Weakness Type (CWE)
Vulnerable Products 1
| Configuration | From (including) | Up to (excluding) |
|---|---|---|
|
Broadcom Rabbitmq_Server
cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*
|
4.2.0
|
4.2.6
|
References 6
https://github.com/rabbitmq/rabbitmq-server/commit/501ad947cd6bbcc9486fe96e0d07…
security-advisories@github.com
https://github.com/rabbitmq/rabbitmq-server/commit/db20d6c0fcf3056030f244b5adab…
security-advisories@github.com
https://github.com/rabbitmq/rabbitmq-server/pull/16092
security-advisories@github.com
https://github.com/rabbitmq/rabbitmq-server/pull/16097
security-advisories@github.com
https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6
security-advisories@github.com
https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-wmrr-4h5v-…
security-advisories@github.com