CVE-2024-29966
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 · uneditedBrocade SANnav OVA before v2.3.1 and v2.3.0a contain hard-coded credentials in the documentation that appear as the appliance's root password. The vulnerability could allow an unauthenticated attacker full access to the 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 confidenceBrocade SANnav OVA virtual appliance versions before v2.3.1 and v2.3.0a contain hard-coded credentials embedded in the product documentation that function as the appliance's root password. An unauthenticated remote attacker who obtains these credentials from the documentation can log in directly as root and gain full administrative control over the SANnav appliance.
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< 2.3.0aCVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Confirm SANnav OVA installationIdentify if the Brocade SANnav virtual appliance is deployed in your environment. This is typically an OVA file imported into VMware or similar virtualization platforms. Check your virtualization inventory for VMs named 'SANnav' or similar.Affected if A SANnav OVA virtual appliance exists in your environment with a version below 2.3.0a
-
Determine SANnav versionAccess the SANnav management interface via web browser or SSH to the appliance, then navigate to the About or System Information section to view the installed version number. Alternatively, log into the appliance console and use 'sannav --version' or check /opt/sannav/version if accessible.Affected if The displayed version is less than 2.3.0a (for example, 2.2.x, 2.1.x, or earlier)
-
Verify root password changedCompare the current root password configured on the SANnav appliance against any credentials that may have been published in product documentation, release notes, or installation guides. Attempt to determine if the original default password from documentation is still in use.Affected if The root password has not been changed from the default credential that was published in the documentation
-
Review access logs for unauthorized root loginsExamine SANnav system logs, authentication logs, or audit logs for successful root login attempts from unexpected IP addresses or at unusual times. Check for any root sessions that you do not recognize.Affected if Unauthorized root-level access is observed in the logs, indicating the hard-coded credentials may have been used by an attacker
You are affected if you are running a SANnav OVA version below 2.3.0a and the root password has not been changed from the default credential published in the product documentation.
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 · scoped2.3.0a
Immediately upgrade to SANnav v2.3.1 or v2.3.0a and change the root password to a unique, strong credential not present in any documentation. Verify no unauthorized access has occurred.
Brocade SANnav v2.3.1 or later
- 1. Download the latest Brocade SANnav OVA from the Broadcom support portal at support.broadcom.com
- 2. Verify the checksum of the downloaded file against the checksum provided on the support site
- 3. Back up the current SANnav configuration and database
- 4. Deploy the new SANnav OVA version 2.3.1 or later
- 5. Restore the backed-up configuration to the new appliance
- 6. Verify that the hard-coded credentials have been removed by attempting to log in with the documented credentials (they should no longer work)
- 7. Set a new strong root password using the SANnav management interface
- 8. Validate normal SANnav operations are functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29966 — 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-29966 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