dbcve.org
Brocade SannavApplication · Broadcom

CVE-2024-2860

HIGH · 7.8 CVSS v3.1 Published 2024-05-08
Fix available
A fix is available. Upgrade to 2.3.0a or later.
See remediation →
80/100
Remediation priority · High
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
The PostgreSQL implementation in Brocade SANnav versions before 2.3.0a is vulnerable to an incorrect local authentication flaw. An attacker accessing the VM where the Brocade SANnav is installed can gain access to sensitive data inside the PostgreSQL database.

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 · moderate confidence

The PostgreSQL implementation in Brocade SANnav versions before 2.3.0a contains an incorrect local authentication flaw. An attacker with access to the VM where Brocade SANnav is installed can bypass authentication to access sensitive data stored in the PostgreSQL database.

MitigationUpgrade Brocade SANnav to version 2.3.0a or later to remediate this vulnerability. Additionally, enforce strict access controls on the VM and restrict physical/network access to prevent unauthorized local attackers from reaching the database.

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= 2.3.1

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 if Brocade SANnav is installed
    Check for Brocade SANnav installation directories or list installed software packages on the system. Common locations include /opt/brocade or check system services for sannav-related processes.
    Affected if Brocade SANnav is found installed on the system
  2. Determine the installed SANnav version
    Locate the SANnav version file or use the SANnav management interface version information. Typically found in the installation directory or accessible via the web management UI login page.
    Affected if The installed version is lower than 2.3.0a OR the version equals exactly 2.3.1
  3. Verify PostgreSQL is accessible locally
    Check if PostgreSQL database service is running and listening on local interfaces. Use commands like 'netstat -tulpn | grep postgres' or 'psql' connection attempts from the local system.
    Affected if PostgreSQL is running and accepts local connections without proper authentication restrictions
  4. Inspect PostgreSQL authentication configuration
    Examine the pg_hba.conf file in the PostgreSQL data directory for authentication settings. Look for 'trust' or 'ident' authentication methods that may allow local bypass.
    Affected if pg_hba.conf contains 'trust' method for local connections or allows password-less local access
  5. Check VM access controls
    Review physical access restrictions and network access controls on the VM hosting SANnav. Verify who has console or SSH access to the system.
    Affected if Unrestricted local access to the VM is possible by unauthorized users

A system is affected if Brocade SANnav version is lower than 2.3.0a or exactly 2.3.1 AND PostgreSQL is accessible locally with weak authentication controls, allowing an attacker with VM access to bypass database authentication.

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.0a or later to remediate this vulnerability. Additionally, enforce strict access controls on the VM and restrict physical/network access to prevent unauthorized local attackers from reaching the database.

Recommended fix Moderate confidence

SANnav version 2.3.2 or later (verify latest available on support.broadcom.com)

  1. 1. Identify the current Brocade SANnav version installed by accessing the SANnav management interface or checking the VM system information.
  2. 2. Navigate to the Broadcom Support Portal at support.broadcom.com and locate the SANnav downloads section.
  3. 3. Download the latest SANnav version (2.3.2 or later) which contains the fix for CVE-2024-2860.
  4. 4. Create a complete backup of the current SANnav VM and export any critical configuration data.
  5. 5. Follow the official SANnav upgrade procedure documented in the Broadcom upgrade guide to install the new version.
  6. 6. After upgrade, verify the PostgreSQL configuration has proper authentication enabled by reviewing the pg_hba.conf file within the SANnav container/VM.
  7. 7. Confirm the SANnav services start successfully and the web interface is accessible.
Caveat Review SANnav release notes for any deprecated features or migration requirements before upgrading; test in non-production environment first

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

Fix this in Brocade Sannav Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-2860 — 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-2860 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