CVE-2022-31008 json
Predictable credential obfuscation seed value used in rabbitmq-server
published 2022-10-06 4 y ago modified 2026-09-08 2 mo ago also BIT-rabbitmq-2022-31008 , EUVD-2022-52713 , GHSA-v9gv-xp36-jgj8
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 34%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- hex rabbit_common 3.8.32, 3.9.18, 3.10.2
- bitnami rabbitmq 3.8.32
- broadcom rabbitmq_server 3.9.18, 3.10.2
- vmware rabbitmq 3.8.32
- rabbitmq-server Debian 14, Debian 13, Debian 12 3.10.8-1
debian advisories DEBIAN-CVE-2022-31008
- elixir115 SLE Module for Server Applications 15 SP6, openSUSE Leap 15.6 1.15.7-150300.7.5.1
- erlang26 SLE Module for Server Applications 15 SP6, openSUSE Leap 15.6 26.2.1-150300.7.5.1
- rabbitmq-server313 SLE Module for Server Applications 15 SP6, openSUSE Leap 15.6 3.13.1-150600.13.5.3
- rabbitmq-server SLE Module for Server Applications 15 SP4, SLE Module for Server Applications 15 SP3, openSUSE Leap 15.4 +1 more 3.8.11-150300.3.11.1
suse advisories SUSE-FU-2024:2078-1SUSE-SU-2022:4378-1
- github.com/rabbitmq/rabbitmq-server@c22e1cb commit
- github.com/rabbitmq/rabbitmq-server#4841 pull request
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-31008 updated cvss 7.5
rabbitmq-server: URI encryption with predictable secret seed
-
Red Hat OpenStack Platform 13 (Queens) rabbitmq-server Red Hat OpenStack Platform 16.1 rabbitmq-server Red Hat OpenStack Platform 16.2 rabbitmq-server Red Hat OpenStack Platform 17.0 rabbitmq-servernot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| hex | rabbit_common | >=3.10.0, <3.10.2 >=3.9.0, <3.9.18 >=3.8.0, <3.8.32 |
3.10.2 3.9.18 3.8.32 |
| bitnami | rabbitmq | <3.8.32 |
3.8.32 |
Affected products
- rabbitmq rabbitmq-server
Classification
References
-
github.com
/rabbitmq/rabbitmq-server/pull/4841
web, patch, third-party-advisory, advisory
-
github.com
/rabbitmq/rabbitmq-server/commit/c22e1cb20e656d211e025c417d1fc75a9067b717
web
-
github.com
/rabbitmq/rabbitmq-server/security/advisories/GHSA-v9gv-xp36-jgj8
web, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-31008
advisory, web
-
github.com
/rabbitmq/rabbitmq-server
package
Sources
- CVE List CVE-2022-31008
- GitHub Advisory GHSA-v9gv-xp36-jgj8
- NVD CVE-2022-31008
- OSV BIT-rabbitmq-2022-31008
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.