By Null Ventures MCP platform
Menu

vulnerability / NVI-00017496 / Revision 1

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

GitHub lists this reviewed advisory for rabbit_common, rabbit_common, rabbit_common. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.

source listedactiveGHSA-v9gv-xp36-jgj8CVE-2022-31008

This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.

01 / Meaning

Why it matters

Published affected context helps an owner decide what evidence to gather. This report has not examined your application.

CVSS

5.5 medium

GitHub source severity; exploitability and local consequence require separate evidence.

As of · GitHub Advisory Database

02 / Applicability

The affected context

Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.

rabbit_common

source listed
  • >= 3.10.0, < 3.10.2

### Impact 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. ### Patches Patched versions: * `3.10.2` * `3.9.18` * `3.8.32` ### 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

GitHub Advisory Database

rabbit_common

source listed
  • >= 3.9.0, < 3.9.18

### Impact 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. ### Patches Patched versions: * `3.10.2` * `3.9.18` * `3.8.32` ### 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

GitHub Advisory Database

rabbit_common

source listed
  • >= 3.8.0, < 3.8.32

### Impact 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. ### Patches Patched versions: * `3.10.2` * `3.9.18` * `3.8.32` ### 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

GitHub Advisory Database

03 / Response

What to do next

  1. investigate

    Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.

    Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database

A fixed release is not deployment evidence.

Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.

04 / Limits

What this report cannot establish

  • Customer inventory, deployment, reachability and exploitation have not been inspected.
Read the collection and interpretation limits ↗

05 / Provenance

Sources you can inspect

Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.

  1. GHSA-v9gv-xp36-jgj8 ↗

    GitHub Advisory Database · vendor advisory

    Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.

Public revision history

Only published revisions appear here. Routine fetches do not create a material-change event.

  1. Revision 1 ·

    First indexed by Null; source disclosure date is shown separately.

Read the public revision data ↗

The next step is private

Bring the question into your environment.

The connected workflow is a development preview for inventory, contextual matching, owner decisions and evidence-based verification. No system-specific result is generated by this page.

See the synthetic workflow preview ↗