LiveActive security incident?Get immediate response
CVE Record

CVE-2020-15378: The OVA version of Brocade SANnav before version 2.1.1 installation with IPv6 networking exposes the docker...

The 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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-15378 concerns Brocade SANnav OVA deployments before version 2.1.1 when IPv6 networking is used. The issue can expose Docker container ports to the network, expanding what an attacker could reach. The source bundle does not provide severity, CVSS, affected ports, or evidence of exploitation.

Executive priority

Treat this as a targeted infrastructure hardening issue, not a confirmed active-exploitation emergency. Organizations using Brocade SANnav OVA should inventory quickly, verify IPv6 exposure, and follow Broadcom remediation guidance because SAN management platforms are high-value operational assets.

Technical view

The vulnerability is an unintended network exposure condition in Brocade SANnav OVA installations before 2.1.1 with IPv6 enabled. Docker container ports may be reachable from the network, increasing attack surface. No CWE, CVSS vector, affected port list, or exploit prerequisites are provided in the supplied sources.

Likely exposure

Exposure appears limited to Brocade SANnav deployed as an OVA before version 2.1.1 with IPv6 networking. Non-OVA deployments or systems without IPv6 are not identified as affected in the supplied bundle.

Exploitation context

The CVE is not listed as KEV in the supplied data, and no cited source states active exploitation. The practical risk depends on whether exposed Docker ports are reachable from untrusted networks and what services are listening.

Researcher notes

The public bundle is sparse: no CVSS, CWE, port list, exploit details, or configuration specifics are included. Analysis should stay centered on the vendor advisory and asset validation. Avoid assuming affected services or exploitability beyond exposed Docker container ports.

Mitigation direction

  • Identify Brocade SANnav OVA deployments and confirm their installed version.
  • Prioritize upgrade or remediation using Broadcom advisory guidance for version 2.1.1 or later.
  • Review IPv6 network exposure for SANnav management systems.
  • Restrict SANnav and container port reachability to trusted administration networks.
  • Monitor vendor guidance for any additional fixes or configuration steps.

Validation and detection

  • Confirm whether the deployment is Brocade SANnav OVA before 2.1.1.
  • Verify whether IPv6 networking is enabled on the affected appliance.
  • Review network policy for exposed Docker container ports.
  • Check whether SANnav management interfaces are reachable from untrusted segments.
  • Document compensating controls and remaining exposure after remediation.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-15378 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aBrocade SANnavBrocade SANnav before version 2.1.1Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.