CVE-2022-28167
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 before Brocade SANvav v. 2.2.0.2 and Brocade SANanv v.2.1.1.8 logs the Brocade Fabric OS switch password in plain text in asyncjobscheduler-manager.log
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 versions prior to 2.2.0.2 and 2.1.1.8 contain a plain-text password logging vulnerability. The application's asyncjobscheduler-manager.log file stores Brocade Fabric OS switch credentials in cleartext, exposing sensitive authentication material to anyone with log file access.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed SANnav versionAccess the SANnav management interface or check the system inventory to determine the current version number of Brocade SANnav installed in your environmentAffected if The version is lower than 2.1.1.8, or falls between 2.2.0.0 and 2.2.0.2 (exclusive)
-
Locate the asyncjobscheduler-manager.log fileNavigate to the SANnav log directory on the application server; the log file is named asyncjobscheduler-manager.log and contains application activity recordsAffected if The log file exists in the expected log directory
-
Examine the log file for plain-text credentialsOpen or search the asyncjobscheduler-manager.log file and look for entries containing switch credentials, usernames, and passwords in cleartext format rather than masked or hashedAffected if The log file contains any Brocade Fabric OS switch usernames or passwords stored in plain text
You are affected if SANnav version is less than 2.1.1.8 or between 2.2.0.0 and 2.2.0.2 AND the asyncjobscheduler-manager.log file contains unencrypted credentials.
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.
From vendor data2.1.1.82.2.0.2
Upgrade Brocade SANnav to version 2.2.0.2, 2.1.1.8, or later to remediate the vulnerability. Review existing log files for exposure and rotate credentials as a precautionary measure.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28167 — 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-28167 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