CVE-2024-5462
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 · uneditedIf Brocade Fabric OS before Fabric OS 9.2.0 configuration settings are not set to encrypt SNMP passwords, then the SNMP privsecret / authsecret fields can be exposed in plaintext. The plaintext passwords can be exposed in a configupload capture or a supportsave capture if encryption of passwords is not enabled. An attacker can use these passwords to fetch values of the supported OIDs via SNMPv3 queries. There are also a limited number of MIB objects that can be modified.
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 confidenceIn Brocade Fabric OS versions before 9.2.0, when SNMP password encryption is not enabled in the configuration settings, the SNMPv3 privsecret and authsecret values are stored and transmitted in plaintext. These plaintext credentials are exposed in configupload or supportsave capture files, allowing attackers to retrieve the passwords and use them for SNMPv3 queries to fetch OID values and modify certain MIB objects.
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< 9.2.0CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check Fabric OS versionRun 'version' or 'firmwareShow' command on the fabric switch to retrieve the installed Fabric OS versionAffected if Version is below 9.2.0 (e.g., 9.1.x, 9.0.x, 8.x, etc.)
-
Verify SNMPv3 configurationRun 'snmpConfig --show v3' to display SNMPv3 settings including authsecret and privsecret parametersAffected if SNMPv3 is enabled with authsecret and privsecret values configured (these are the credentials at risk)
-
Check SNMP password encryption statusRun 'snmpConfig --show encryption' or inspect the configuration for the password encryption settingAffected if SNMP password encryption is disabled or not set (this is the vulnerable condition)
-
Inspect configupload or supportsave filesExamine any previously generated configupload or supportsave files for plaintext authsecret and privsecret valuesAffected if Plaintext SNMPv3 passwords are present in these files (confirms active exposure)
You are affected if running Fabric OS below 9.2.0 with SNMPv3 configured and password encryption disabled, as plaintext credentials can be retrieved from config files.
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 · scoped9.2.0
Enable SNMP password encryption in Fabric OS configuration settings and upgrade to Fabric OS 9.2.0 or later to remediate this vulnerability.
Fabric OS 9.2.0 or later
- 1. Upgrade Brocade Fabric Operating System to version 9.2.0 or later to receive the security fix.
- 2. After upgrade, verify SNMP configuration settings enable password encryption using the CLI command: `snmpconfig --set snmpv3` or via Fabric Web tools.
- 3. For existing installations that cannot immediately upgrade, ensure SNMP password encryption is enabled in configuration settings before performing configupload or supportsave operations.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5462 — 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-5462 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