CVE-2020-15381
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 version 2.1.1 contains an Improper Authentication vulnerability that allows cleartext transmission of authentication credentials of the jmx server.
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 before 2.1.1 contain an Improper Authentication vulnerability in the jmx server component where authentication credentials are transmitted in cleartext, enabling credential interception through network sniffing or man-in-the-middle attacks.
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.1CVSS 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.
-
Identify SANnav installation and versionLocate the SANnav installation directory or use system inventory tools to find the installed version of Brocade/Broadcom SANnav. Common methods include checking /opt/sannav or using 'rpm -q' or 'dpkg -l' commands if installed via package manager.Affected if The installed version is found to be lower than 2.1.1
-
Confirm jmx server is enabledCheck SANnav configuration files or running services to determine if the jmx server component is active. This may involve reviewing process listings, service configurations, or management console settings.Affected if The jmx server component is running and accessible on the network
-
Verify network exposure of jmx portIdentify the jmx server port (commonly port 8080 or 8443 for management interfaces) using netstat or similar network scanning tools. Determine if the port is listening on external interfaces rather than localhost only.Affected if The jmx port is exposed to network segments where untrusted users could intercept traffic
-
Capture network traffic to jmx serverUse packet capture tools (tcpdump, Wireshark) to capture traffic flowing to the jmx server port during authentication. Analyze the capture to check if credentials appear in plaintext within the network packets.Affected if Authentication credentials are observed in cleartext within captured network traffic
-
Review jmx server authentication configurationExamine SANnav configuration files related to jmx authentication settings. Look for transport configuration that specifies whether SSL/TLS encryption is enabled for the jmx connector.Affected if SSL/TLS encryption is not enabled or is explicitly disabled for jmx authentication
You are affected if SANnav version is below 2.1.1 AND the jmx server is accessible over the network with cleartext authentication enabled.
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
Upgrade Brocade SANnav to version 2.1.1 or later to implement proper encryption for jmx server authentication credentials.
- Consultation2.0 h
- Implementation4.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15381 — 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-15381 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