CVE-2020-15378
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 · uneditedThe OVA version of Brocade SANnav before version 2.1.1 installation with IPv6 networking exposes the docker container ports to the network, increasing the potential attack surface.
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 confidenceThe OVA version of Brocade SANnav before version 2.1.1, when deployed with IPv6 networking, exposes Docker container ports directly to the network rather than maintaining proper network isolation. This allows potentially unauthorized network access to services running inside the Docker containers.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Confirm SANnav OVA deploymentIdentify if the system is running the OVA (virtual appliance) version of Brocade SANnav. This is typically the default deployment method for SANnav.Affected if System is not running the SANnav OVA virtual appliance format
-
Check installed SANnav versionLocate and read the SANnav version information, typically accessible through the SANnav web interface (usually at https://<hostname>:8443/sannav) under About or System settings, or via CLI if available. Compare the installed version to the affected range of versions prior to 2.1.1.Affected if Installed version is earlier than 2.1.1 (for example, 2.1.0, 2.0.x, or earlier)
-
Verify IPv6 networking is enabledCheck the network configuration of the SANnav OVA virtual machine to determine if IPv6 is configured and active. This can be done through the hypervisor management console (vSphere, Hyper-V, etc.) by reviewing the VM network adapter settings, or by logging into the SANnav OVA and running network diagnostic commands to check for IPv6 addresses or interfaces.Affected if IPv6 networking is enabled and the system has an active IPv6 address or interface
-
Inspect Docker container port exposureFrom within the SANnav OVA (via SSH or console access), examine Docker container configurations and running containers to identify if container ports (such as those for MySQL, Redis, Tomcat, or other services) are bound to 0.0.0.0 or ::: instead of being restricted to localhost or internal Docker networks. Use commands such as 'docker ps' and 'docker inspect <container_id>' to review port mappings and bind addresses.Affected if Docker containers have ports exposed to 0.0.0.0 or all interfaces, allowing external network access rather than being isolated to internal networks only
A system is affected if it is running SANnav OVA version earlier than 2.1.1 with IPv6 networking enabled, and Docker container ports are exposed to the network instead of being properly isolated.
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 obtain the fixed version, or implement network segmentation and firewall rules to restrict access to the exposed Docker ports if upgrading is not immediately feasible.
- 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-2020-15378 — 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-15378 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