CVE-2022-31008

RabbitMQ has predictable credential obfuscation seed value used in Shovel and Federation plugins

Workarounds

Disable Shovel and Federation plugins.

Credits

RabbitMQ core team would like to thank Lajos @luos Gerecs and Anh Nguyen from Erlang Solutions
for responsibly disclosing and working with us on a patch for this vulnerability.

For more information

• Mailing list
• Community Slack

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.

Security-sensitive operations rely on values that are predictable or insufficiently random. Typical impact: forged tokens, guessable identifiers, or broken cryptographic protocols.

CVE-2022-31008 has a CVSS score of 5.5 (Medium). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.10.2, 3.9.18, 3.8.32); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Patched versions:

• 3.10.2
• 3.9.18
• 3.8.32

1. What is CVE-2022-31008? CVE-2022-31008 is a medium-severity use of insufficiently random values vulnerability in rabbit_common (erlang), affecting versions >= 3.10.0, < 3.10.2. It is fixed in 3.10.2, 3.9.18, 3.8.32. Security-sensitive operations rely on values that are predictable or insufficiently random.
2. How severe is CVE-2022-31008? CVE-2022-31008 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of rabbit_common are affected by CVE-2022-31008? rabbit_common (erlang) versions >= 3.10.0, < 3.10.2 is affected.
4. Is there a fix for CVE-2022-31008? Yes. CVE-2022-31008 is fixed in 3.10.2, 3.9.18, 3.8.32. Upgrade to this version or later.
5. Is CVE-2022-31008 exploitable, and should I be worried? Whether CVE-2022-31008 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-31008 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-31008?
   • Upgrade rabbit_common to 3.10.2 or later
   • Upgrade rabbit_common to 3.9.18 or later
   • Upgrade rabbit_common to 3.8.32 or later

Other vulnerabilities in rabbit_common