dbcve.org
Brocade SannavApplication · Broadcom

CVE-2024-29961

HIGH · 8.2 CVSS v3.1 Published 2024-04-19
Fix available
A fix is available. Upgrade to 2.3.0a or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability affects Brocade SANnav before v2.3.1 and v2.3.0a. It allows a Brocade SANnav service to send ping commands in the background at regular intervals to gridgain.com to check if updates are available for the Component. This could make an unauthenticated, remote attacker aware of the behavior and launch a supply-chain attack against a Brocade SANnav appliance.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Brocade SANnav versions before v2.3.1 and v2.3.0a contain a background service that periodically sends ping/update-check requests to gridgain.com. This outbound network behavior can be observed by an unauthenticated remote attacker, revealing the presence of a Brocade SANnav appliance and enabling potential supply-chain attacks through DNS hijacking or man-in-the-middle interception of the update mechanism.

MitigationUpgrade Brocade SANnav to version 2.3.1 or v2.3.0a, and implement network segmentation or firewall rules to restrict outbound connections from the appliance to only authorized update sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Brocade SannavApplication
Affected:< 2.3.0a

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SANnav installation and version
    Locate the Brocade SANnav installation directory and check the version file or use the product's version command. Compare the installed version against the affected range (versions before 2.3.0a).
    Affected if The installed version is before 2.3.0a (or any version less than 2.3.0a).
  2. Monitor outbound network traffic to gridgain.com
    Use network monitoring tools (such as tcpdump, Wireshark, or network firewall logs) to capture and inspect outbound connections from the SANnav appliance. Look for DNS queries to gridgain.com or HTTP/HTTPS connections to gridgain.com endpoints.
    Affected if Outbound connections to gridgain.com are observed from the SANnav appliance.
  3. Review DNS query logs for gridgain.com
    Examine DNS server logs or the appliance's DNS resolution cache for queries to the domain gridgain.com. Check both recursive DNS servers and the appliance's local DNS resolver.
    Affected if DNS queries for gridgain.com originating from the SANnav appliance are logged.
  4. Inspect scheduled tasks or background services
    Review the SANnav appliance for scheduled tasks, cron jobs, or background services related to update checking, ping, or telemetry. Look for any configuration files that reference gridgain.com as an update or ping destination.
    Affected if A background service, scheduled task, or configuration file references gridgain.com as an update or ping endpoint.

A user is affected if the SANnav version is before 2.3.0a and outbound network traffic to gridgain.com is observed from the appliance, indicating the vulnerable background update service is active.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.3.0a or later
Fixed in 2.3.0a
Interim mitigation

Upgrade Brocade SANnav to version 2.3.1 or v2.3.0a, and implement network segmentation or firewall rules to restrict outbound connections from the appliance to only authorized update sources.

Recommended fix High confidence

Brocade SANnav v2.3.1 or later

  1. 1. Back up the current Brocade SANnav configuration and data according to your backup procedures.
  2. 2. Download the latest SANnav version (v2.3.1 or later) from the Broadcom support portal at support.broadcom.com.
  3. 3. Follow the official Brocade SANnav upgrade documentation to apply the update.
  4. 4. Verify the upgrade was successful by logging into the SANnav management interface.
  5. 5. Confirm that the background ping to gridgain.com no longer occurs by monitoring network traffic or reviewing system logs.
Caveat Review release notes for any configuration or feature changes between your current version and v2.3.1; test in a non-production environment first if possible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Brocade Sannav Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29961 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-29961 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data