CVE-2024-5461
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 · uneditedImplementation of the Simple Network Management Protocol (SNMP) operating on the Brocade 6547 (FC5022) embedded switch blade, makes internal script calls to system.sh from within the SNMP binary. An authenticated attacker could perform command or parameter injection on SNMP operations that are only enabled on the Brocade 6547 (FC5022) embedded switch. This injection could allow the authenticated attacker to issue commands as Root.
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 confidenceThe SNMP implementation on Brocade 6547 (FC5022) embedded switch blades makes internal script calls to system.sh from within the SNMP binary. An authenticated attacker can inject commands or parameters through SNMP operations, achieving arbitrary command execution as root.
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< 8.2.3e1CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelCheck the switch model via console, CLI (show chassis or show version), or management interface. Look for Brocade 6547 or FC5022 in the hardware inventory.Affected if Device is a Brocade 6547 or FC5022 embedded switch blade
-
Check the Fabric OS versionExecute 'version' or 'show firmware' via CLI to retrieve the Broadcom Fabric Operating System version. Compare against the affected range of < 8.2.3e1.Affected if Fabric OS version is lower than 8.2.3e1
-
Verify if SNMP is enabledRun 'snmpconfig --show' or check SNMP settings via the management interface. Look for SNMPv1/v2c or SNMPv3 status.Affected if SNMP is enabled and accessible
-
Review SNMP community strings and access controlsExecute 'snmpconfig' to list community strings and access settings. Check if default communities (like public/private) are in use and which IPs are permitted for SNMP access.Affected if Default or weak SNMP communities are configured, or SNMP is accessible from untrusted networks
-
Inspect SNMP MIB structures for anomaliesUse snmpwalk to query the device and review any custom MIBs or unexpected OID responses that might indicate modified SNMP scripts or configurations.Affected if Unexpected OIDs or custom script references appear in SNMP queries
A system is affected if it is a Brocade 6547/FC5022 running Broadcom Fabric OS below version 8.2.3e1 with SNMP enabled and accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scoped8.2.3e1
Apply vendor-provided firmware patches when available; until then, restrict SNMP access to trusted IPs only, disable unnecessary SNMP operations, and monitor for anomalous SNMP activity.
Fabric Operating System 8.2.3e1 or later
- 1. Identify the current Fabric Operating System version running on the Brocade 6547 (FC5022) embedded switch using 'version' or 'switchnode' command
- 2. Navigate to support.broadcom.com and locate the Fabric OS version 8.2.3e1 or later for the FC5022 switch
- 3. Download the appropriate firmware upgrade file for your specific hardware model
- 4. Follow Broadcom's standard Fabric OS upgrade procedure: typically upload the firmware to the switch using FTP/SCP, then execute 'firmwaredownload' or 'firmwareupgrade' command
- 5. Verify the upgrade was successful by checking the new version with 'version' command
- 6. Validate that SNMP operations function correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5461 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-5461 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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