dbcve.org
Fabric Operating SystemOperating system · Broadcom

CVE-2024-5460

HIGH · 8.1 CVSS v3.1 Published 2024-06-26
Fix available
A fix is available. Upgrade to 9.0.0 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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 in the default configuration of the Simple Network Management Protocol (SNMP) feature of Brocade Fabric OS versions before v9.0.0 could allow an authenticated, remote attacker to read data from an affected device via SNMP. The vulnerability is due to hard-coded, default community string in the configuration file for the SNMP daemon. An attacker could exploit this vulnerability by using the static community string in SNMP version 1 queries to an affected device.

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

A hard-coded default community string in the SNMP daemon configuration file of Brocade Fabric OS (versions before v9.0.0) allows authenticated remote attackers to read device data via SNMPv1 queries using this static community string.

MitigationReplace the hard-coded default community string with a unique, complex custom community string in the SNMP configuration and verify all legitimate SNMP monitoring continues to function.

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
Fabric Operating SystemOperating system
Affected:< 9.0.0

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

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

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. Determine Fabric OS version
    Run the command to display the Fabric OS version (typically 'version' or 'firmwareShow' via CLI). Compare the installed version against the affected range of versions before v9.0.0.
    Affected if The installed version is below 9.0.0 (for example, 8.2.x, 7.x, etc.)
  2. Verify SNMP daemon is enabled
    Check the SNMP configuration to confirm the SNMP daemon is actively running or enabled on the device.
    Affected if SNMP is enabled and running on the Fabric OS device.
  3. Examine SNMP community string configuration
    Access the SNMP daemon configuration file or use the appropriate command to view the configured community strings (commonly via snmpconfig or similar utility).
    Affected if A hard-coded default community string (such as 'public', 'private', or vendor默认值) is configured and in use.
  4. Confirm community string is the default
    Compare the active community string against known default values that ship with Fabric OS. If the string matches common defaults, it indicates the hard-coded string is present.
    Affected if The community string matches the hard-coded default value that was shipped with the affected Fabric OS versions.

The environment is affected if the Fabric OS version is below 9.0.0, SNMP is enabled, and the configured community string is the hard-coded default value rather than a unique custom string.

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 9.0.0 or later
Fixed in 9.0.0
Interim mitigation

Replace the hard-coded default community string with a unique, complex custom community string in the SNMP configuration and verify all legitimate SNMP monitoring continues to function.

Recommended fix High confidence

Fabric OS v9.0.0 or later

  1. Identify the current Fabric OS version using 'version' command or via web management interface
  2. Review current SNMP configuration using 'snmpConfig --show' command
  3. Plan upgrade to Fabric OS v9.0.0 or later following Broadcom upgrade procedures from support.broadcom.com
  4. Perform upgrade during maintenance window following standard Brocade upgrade process
  5. After upgrade, verify SNMP configuration has been updated: run 'snmpConfig --show' to confirm default community strings have been changed from hard-coded values
  6. Configure custom SNMP community strings using 'snmpConfig --set' command to replace any remaining default values
  7. Verify SNMP functionality works with new community strings
Caveat Major version upgrades may introduce compatibility changes; review Brocade release notes for Fabric OS v9.0.0 for any configuration or feature changes

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

Fix this in Fabric Operating System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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