CVE-2022-28168
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 · uneditedIn Brocade SANnav before Brocade SANnav v2.2.0.2 and Brocade SANnav2.1.1.8, encoded scp-server passwords are stored using Base64 encoding, which could allow an attacker able to access log files to easily decode the passwords.
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 stores SCP server passwords using Base64 encoding rather than proper encryption. Since Base64 is easily reversible encoding (not encryption), an attacker with access to log files containing these encoded passwords can trivially decode them to obtain the plaintext credentials.
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.1.1.8>= 2.2.0.0, < 2.2.0.2CVSS 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.
-
Determine SANnav installed versionAccess the SANnav management interface and navigate to Help > About, or check the version via the application launcher/console. Alternatively, check the installation directory for a version file or check the application startup logs.Affected if The installed version is less than 2.1.1.8, or is 2.2.0.0 or 2.2.0.1 (falls within < 2.1.1.8 or >= 2.2.0.0, < 2.2.0.2)
-
Locate SANnav log directoriesNavigate to the SANnav installation directory and find the logs folder. Common paths include <install_dir>/logs or <install_dir>/SANnav<version>/logs. Review directory listing for log files.Affected if Log files exist and are accessible to unauthorized users or have been shared externally
-
Search logs for Base64-encoded password patternsUse grep or a text search utility to search log files for strings resembling Base64 patterns (look for alphanumeric strings of appropriate length that repeat or appear near 'SCP', 'password', or 'credential' keywords). Example grep pattern: grep -r 'password\|credential\|SCP' /path/to/logs/ | grep -E '[A-Za-z0-9+/=]{20,}'Affected if Log files contain Base64-encoded strings that correspond to SCP server passwords (the strings can be decoded using standard Base64 decoding to reveal plaintext credentials)
A user is affected if their SANnav version is below 2.1.1.8 or between 2.2.0.0 and 2.2.0.1 inclusive, AND log files containing Base64-encoded SCP passwords are accessible or have been exposed.
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.1.1.82.2.0.2
Upgrade to Brocade SANnav v2.2.0.2 or v2.1.1.8 or later. As a precautionary measure, rotate all SCP server passwords after applying the update since they may have been exposed in logs.
Brocade SANnav v2.1.1.8 or v2.2.0.2 (or subsequent releases)
- 1. Check the current version of Brocade SANnav installation
- 2. If running a version < 2.1.1.8 or >= 2.2.0.0 and < 2.2.0.2, plan for upgrade
- 3. Upgrade to Brocade SANnav v2.1.1.8 or v2.2.0.2 (or later stable release)
- 4. After upgrade, rotate SCP server credentials that may have been logged and potentially exposed
- 5. Review log files for any unauthorized access during the vulnerable period
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28168 — 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-2022-28168 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