CVE-2022-31008: Predictable credential obfuscation seed value used in rabbitmq-server
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.39% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: rabbitmq-server (Debian:12) 3.10.8-1; rabbit_common (Hex) 3.10.2, 3.8.32, 3.9.18; rabbitmq-server (openSUSE:Leap 15.3) 3.8.11-150300.3.11.1.
- Severity is disputed: the assigning authority (CNA) scores it 5.5, NVD 7.5.
Low priority for now. Upgrade to rabbitmq-server (Debian:12) 3.10.8-1; rabbit_common (Hex) 3.10.2, 3.8.32, 3.9.18; rabbitmq-server (openSUSE:Leap 15.3) 3.8.11-150300.3.11.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 6, 2022
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 33th percentile
- CWE
- CWE-330
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.5
- CNA · GitHub_M
- 5.5
- 2.0 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| broadcom | rabbitmq server | cpe:2.3:a:broadcom:rabbitmq_server |
| vmware | rabbitmq | cpe:2.3:a:vmware:rabbitmq |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- broadcom rabbitmq server3.9.0 and later · before 3.9.18
- broadcom rabbitmq server3.10.0 and later · before 3.10.2
- vmware rabbitmqbefore 3.8.32
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
rabbitmq rabbitmq-server
- < 3.8.32, >= 3.9.0, < 3.9.18, >= 3.10.0, < 3.10.2affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | rabbitmq-server | before 3.10.8-1 | 3.10.8-1 |
| Hex | rabbit_common | from 3.10.0 · before 3.10.2 | 3.10.2 |
| Hex | rabbit_common | from 3.8.0 · before 3.8.32 | 3.8.32 |
| Hex | rabbit_common | from 3.9.0 · before 3.9.18 | 3.9.18 |
| openSUSE:Leap 15.3 | rabbitmq-server | before 3.8.11-150300.3.11.1 | 3.8.11-150300.3.11.1 |
| openSUSE:Leap 15.6 | elixir115 | before 1.15.7-150300.7.5.1 | 1.15.7-150300.7.5.1 |
| openSUSE:Leap 15.6 | erlang26 | before 26.2.1-150300.7.5.1 | 26.2.1-150300.7.5.1 |
| openSUSE:Leap 15.6 | rabbitmq-server313 | before 3.13.1-150600.13.5.3 | 3.13.1-150600.13.5.3 |
| SUSE:Linux Enterprise Module for Server Applications 15 SP3 | rabbitmq-server | before 3.8.11-150300.3.11.1 | 3.8.11-150300.3.11.1 |
| SUSE:Linux Enterprise Module for Server Applications 15 SP6 | elixir115 | before 1.15.7-150300.7.5.1 | 1.15.7-150300.7.5.1 |
| SUSE:Linux Enterprise Module for Server Applications 15 SP6 | erlang26 | before 26.2.1-150300.7.5.1 | 26.2.1-150300.7.5.1 |
| SUSE:Linux Enterprise Module for Server Applications 15 SP6 | rabbitmq-server313 | before 3.13.1-150600.13.5.3 | 3.13.1-150600.13.5.3 |
Same product
broadcom: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-57216RabbitMQ: AMQP 1.0, AMQP 0-9-1, Stream Protocol loopback enforcement can lead to remote guest sessions due to listener-address loopback checks40Plan
- CVE-2026-57211RabbitMQ: UNC SSRF affecting the management UI on Windows40Plan
- CVE-2016-9877An issue was discovered in Pivotal RabbitMQ 3.x before 3.5.8 and 3.6.x before 3.6.6 and RabbitMQ for PCF 1.5.x before 1.5.20, 1.6.x before 139Monitor
Published before and after this one in the same product
- ← EarlierCVE-2020-5419Aug 31, 2020 · RabbitMQ arbitrary code execution using local binary planting26Monitor
- ← EarlierCVE-2021-22117May 18, 2021 · RabbitMQ installers on Windows prior to version 3.8.16 do not harden plugin directory permissions, potentially allowing attackers with suffi31Monitor
- Later →CVE-2025-50200Jun 19, 2025 · RabbitMQ Node can log Basic Auth header from an HTTP request26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:rabbitmq-server | 3.10.8-1 · Debian:12 | Package registry (OSV) |
| Hex:rabbit_common | 3.10.2 | Package registry (OSV) |
| Hex:rabbit_common | 3.8.32 | Package registry (OSV) |
| Hex:rabbit_common | 3.9.18 | Package registry (OSV) |
| opensuse:elixir115 | 1.15.7-150300.7.5.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:erlang26 | 26.2.1-150300.7.5.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:rabbitmq-server | 3.8.11-150300.3.11.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:rabbitmq-server313 | 3.13.1-150600.13.5.3 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:elixir115 | 1.15.7-150300.7.5.1 · SUSE:Linux Enterprise Module for Server Applications 15 SP6 | Package registry (OSV) |
| suse:erlang26 | 26.2.1-150300.7.5.1 · SUSE:Linux Enterprise Module for Server Applications 15 SP6 | Package registry (OSV) |
| suse:rabbitmq-server | 3.8.11-150300.3.11.1 · SUSE:Linux Enterprise Module for Server Applications 15 SP3 | Package registry (OSV) |
| suse:rabbitmq-server313 | 3.13.1-150600.13.5.3 · SUSE:Linux Enterprise Module for Server Applications 15 SP6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-330 · Use of Insufficiently Random ValuesCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.