CVE-2020-15370
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 Fabric OS versions before Brocade Fabric OS v7.4.2g could allow an authenticated, remote attacker to view a user password in cleartext. The vulnerability is due to incorrectly logging the user password in log files.
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 confidenceIn Brocade Fabric OS versions prior to 7.4.2g, user passwords are being written in plaintext to log files due to incorrect logging implementation. An authenticated remote attacker who gains access to these log files can recover plaintext user 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< 7.4.2gCVSS 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.
-
Check the Fabric OS versionRun the command 'version' or 'firmwareShow' on the Fabric OS CLI to display the current firmware versionAffected if The displayed version is less than 7.4.2g (for example, 7.4.2f, 7.4.1, 7.3.x, or earlier)
-
Identify log files on the systemNavigate to the log directory (commonly /var/log/ or the configured syslog location) and list all log files present on the Fabric OS deviceAffected if Log files exist and the system is running a version below 7.4.2g
-
Search log files for plaintext password patternsUse grep or a text search tool to search log files for strings that resemble passwords, such as 'password=', 'passwd=', or visible plaintext credentials. Example: grep -i 'password' /var/log/*Affected if Any log file contains plaintext password strings and the version is below 7.4.2g
-
Review authentication logs for credential exposureExamine authentication-related log files (such as auth.log, audit.log, or similar) for any entries that may have logged user credentials during login or configuration eventsAffected if Authentication logs contain plaintext user credentials and the version is vulnerable
A system is affected if it runs Fabric OS version prior to 7.4.2g AND contains log files with plaintext passwords written due to the incorrect logging implementation.
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 data7.4.2g
Upgrade Brocade Fabric OS to version 7.4.2g or later to receive the patch that prevents passwords from being logged in cleartext. Review existing log files for exposed credentials and rotate compromised passwords as a precaution.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15370 — 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-2020-15370 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