dbcve.org
SannavApplication · Brocade

CVE-2022-28161

MEDIUM · 5.5 CVSS v3.1 Published 2022-05-09
Fix available
A fix is available. Upgrade to 2.2.0 or later.
See remediation →
57/100
Remediation priority · Elevated
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
An information exposure through log file vulnerability in Brocade SANNav versions before Brocade SANnav 2.2.0 could allow an authenticated, local attacker to view sensitive information such as ssh passwords in filetansfer.log in debug mode. To exploit this vulnerability, the attacker would need to have valid user credentials and turn on debug mode.

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

In Brocade SANNav versions before 2.2.0, debug mode logging writes sensitive information including SSH passwords in plaintext to the filetansfer.log file. An authenticated local attacker with valid credentials who enables debug mode can read this log file to obtain sensitive authentication credentials.

MitigationUpgrade to Brocade SANNav 2.2.0 or later. Until patched, limit access to debug mode settings and restrict unauthorized access to log file directories.

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
SannavApplication
Affected:< 2.2.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check SANNav installed version
    Locate the SANNav application version through the product's web interface, command line, or system information. This is typically found in the About section or by querying the application directly.
    Affected if The installed version is any release before 2.2.0 (versions 1.x, 2.0.x, or earlier)
  2. Verify debug mode status
    Access the SANNav administrative settings or configuration panel. Look for debug mode, logging level, or diagnostic settings. Check whether debug mode is currently enabled or has been enabled historically.
    Affected if Debug mode is currently enabled or was enabled at any point since installation
  3. Locate the filetansfer.log file
    Search the SANNav installation directory, log directory, or file system for a file named 'filetansfer.log'. This file is created when debug mode logging is active.
    Affected if The filetansfer.log file exists on the system
  4. Examine log for plaintext credentials
    Open or parse the filetansfer.log file using a text viewer or editor. Search within the file contents for strings that resemble passwords, SSH credentials, or authentication tokens in plaintext format.
    Affected if The log file contains plaintext SSH passwords or other sensitive authentication credentials

A system is affected if it runs any Brocade SANNav version before 2.2.0 with debug mode enabled and the filetansfer.log file contains plaintext SSH credentials.

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

Upgrade to Brocade SANNav 2.2.0 or later. Until patched, limit access to debug mode settings and restrict unauthorized access to log file directories.

Recommended fix High confidence

Brocade SANNav 2.2.0

  1. Download Brocade SANNav version 2.2.0 or later from Broadcom's official support portal
  2. Review the SANNav upgrade documentation and best practices
  3. Create a complete backup of the current SANNav configuration
  4. Install or upgrade to SANNav version 2.2.0 following the documented upgrade procedure
  5. After upgrading, verify the fix by confirming that sensitive information such as SSH passwords is no longer being written to filetansfer.log in debug mode
  6. Ensure debug mode is only enabled when necessary for troubleshooting purposes

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

Fix this in Sannav Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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