CVE-2022-31008: RabbitMQ is a multi-protocol messaging and streaming broker.
High CVSS 7.5
- CVE id
- CVE-2022-31008
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| RabbitMQ Runtimes and servers |
>= 3.9.0, < 3.9.18 >= 3.10.0, < 3.10.2 < 3.8.32 |
3.8.32, 3.9.18, 3.10.2 |
How to fix it
Upgrade RabbitMQ to the fixed release of the line you run: 3.8.32, 3.9.18, 3.10.2.
rabbitmqctl version
- Upgrade RabbitMQ (the rabbitmq image tag or the rabbitmq-server package) to the patched release, node by node.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
RabbitMQ is a multi-protocol messaging and streaming broker. In affected versions the shovel and federation plugins perform URI obfuscation in their worker (link) state. The encryption key used to encrypt the URI was seeded with a predictable secret. This means that in case of certain exceptions related to Shovel and Federation plugins, reasonably easily deobfuscatable data could appear in the node log. Patched versions correctly use a cluster-wide secret for that purpose. This issue has been addressed and Patched versions: 3.10.2, 3.9.18, 3.8.32 are available. Users unable to upgrade should disable the Shovel and Federation plugins.
References
- CVE-2022-31008 on the NVD
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2022-31008
- Web: https://github.com/rabbitmq/rabbitmq-server/pull/4841
- Web: https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-v9gv-xp36-jgj8
- Web: https://github.com/rabbitmq/rabbitmq-server/pull/4841
- Web: https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-v9gv-xp36-jgj8
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.