dbcve.org
Fabric Operating SystemOperating system · Broadcom

CVE-2022-28170

MEDIUM · 6.5 CVSS v3.1 Published 2022-10-25
Fix available
A fix is available. Upgrade to 7.4.2j / 8.2.3c or later.
See remediation →
67/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
Brocade Fabric OS Web Application services before Brocade Fabric v9.1.0, v9.0.1e, v8.2.3c, v7.4.2j store server and user passwords in the debug statements. This could allow a local user to extract the passwords from a debug file.

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

Brocade Fabric OS Web Application services write server and user passwords to debug log files. A local authenticated user with file system access can read these debug files and extract plaintext credentials, potentially gaining elevated access to the system or connected infrastructure.

MitigationUpgrade Brocade Fabric OS to version 9.1.0, 9.0.1e, 8.2.3c, or 7.4.2j or later. Additionally, rotate any credentials that may have been exposed in debug logs since the vulnerability was present.

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
Fabric Operating SystemOperating system
Affected:< 7.4.2j>= 8.0.0, < 8.2.3c>= 9.0.0, < 9.0.1e= 9.1.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
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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 the Fabric OS version
    Run the command `version` or `firmwareversion` on the Fabric OS device to obtain the currently installed version number.
    Affected if The installed version falls within the affected ranges: below 7.4.2j, 8.0.0 through 8.2.3b, 9.0.0 through 9.0.1d, or exactly 9.1.0.
  2. Identify Web Application service debug logs
    Locate debug log files for the Fabric OS Web Application services. Check common log directories such as /var/log, /fabos/log, or similar paths where Fabric OS stores service logs.
    Affected if Debug log files exist and are readable by authenticated users, indicating credentials may have been written to them.
  3. Inspect log file contents for credentials
    Search the identified debug log files for patterns indicating plaintext passwords, such as strings containing 'password', 'passwd', or credential assignments. Use commands like `grep -i password <logfile>` on suspect files.
    Affected if Plaintext server or user passwords are found within the debug log files.
  4. Verify file permissions on log directories
    Check the permissions on directories containing Web Application debug logs using `ls -la` or similar commands. Verify which system users have read access to these log files.
    Affected if Log files or directories are readable by non-privileged authenticated users, allowing credential extraction.

You are affected if your Fabric OS version is within the vulnerable ranges and debug log files containing plaintext passwords exist and are accessible on your system.

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 7.4.2j / 8.2.3c / 9.0.1e or later
Fixed in 7.4.2j8.2.3c9.0.1e
Interim mitigation

Upgrade Brocade Fabric OS to version 9.1.0, 9.0.1e, 8.2.3c, or 7.4.2j or later. Additionally, rotate any credentials that may have been exposed in debug logs since the vulnerability was present.

Recommended fix High confidence

7.4.2j (7.x branch), 8.2.3c (8.x branch), 9.0.1e (9.0.x branch), or 9.1.1+ (9.1.x branch)

  1. 1. Identify the current Fabric OS version running on the affected Brocade fabric switches using the 'version' or 'firmwareShow' command.
  2. 2. Based on the current version, plan the upgrade to the appropriate fixed release: For 7.x branch: upgrade to 7.4.2j or later; For 8.0.x-8.2.x branch: upgrade to 8.2.3c or later; For 9.0.x branch: upgrade to 9.0.1e or later; For 9.1.0: upgrade to 9.1.1 or later.
  3. 3. Download the firmware from the Broadcom support portal (support.broadcom.com) after authenticating with valid support credentials.
  4. 4. Follow the standard Fabric OS firmware upgrade procedure: Transfer the firmware to the switch using FTP/SCP, verify the firmware integrity, execute 'firmwareDownload' command, and allow the switch to reboot.
  5. 5. After upgrade, verify the new version is running using 'version' command.
  6. 6. Review any existing debug logs for exposure and sanitize or remove them if they may contain sensitive information.
  7. 7. Ensure proper file permissions are in place on any debug output directories.
Caveat Standard Fabric OS upgrade risks apply - ensure failover redundancy is configured and follow Broadcom recommended upgrade procedures to avoid disruption

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

Fix this in Fabric Operating System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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