CVE-2024-29955
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 · uneditedA vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a could allow a privileged user to print the SANnav encrypted key in PostgreSQL startup logs. This could provide attackers with an additional, less-protected path to acquiring the encryption key.
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 confidenceA vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a allows privileged users to print the SANnav encrypted key in PostgreSQL startup logs. This exposes the encryption key through an unintended logging path, providing attackers with an additional, less-protected avenue to acquire the key.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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.
-
Determine the installed Brocade SANnav versionAccess the SANnav management interface or use the product's version information method to identify the currently installed versionAffected if The installed version is before v2.3.0a or v2.3.1 (specifically any version earlier than 2.3.0a)
-
Locate PostgreSQL service startup logsFind the PostgreSQL log files that are generated when the SANnav database service initializes. These logs are typically stored in the SANnav installation directory or standard PostgreSQL log locationsAffected if PostgreSQL startup logs exist and are accessible for review
-
Search for encryption key content in logsReview the PostgreSQL startup logs and look for strings that resemble the SANnav encrypted key or any sensitive credential material that should not be present in diagnostic outputAffected if The SANnav encrypted key or sensitive authentication material is found written to the PostgreSQL startup logs
You are affected if your SANnav version is earlier than v2.3.0a and the encrypted key appears in the PostgreSQL startup log files, indicating it was exposed through this unintended logging path
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
Upgrade to Brocade SANnav v2.3.1 or v2.3.0a (depending on the applicable fix version) to resolve the vulnerability. Prior to upgrade, back up configurations and test in a non-production environment.
SANnav v2.3.1 or later
- 1. Back up the current SANnav configuration and database following the official backup procedures.
- 2. Download the fixed SANnav version (v2.3.1 or later) from the Broadcom support portal at support.broadcom.com.
- 3. Stop the SANnav services using the official shutdown procedure.
- 4. Install the SANnav v2.3.1 (or later) upgrade package using the standard upgrade process.
- 5. Verify the installation completed successfully by checking the version number in the SANnav management interface.
- 6. Confirm that PostgreSQL startup logs no longer contain the encrypted key by reviewing the logs.
- 7. Restart SANnav services and verify normal operation.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29955 — 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-29955 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