Container service exposure via unrestricted IPv6 networking
Published Jun 9, 2021 · Updated Aug 4, 2024
Network exposure in Brocade SANnav before 2.1.1 allows attackers to reach Docker container ports through IPv6 networking. IPv6 configuration during OVA installation or through change-ipv4-installation-to-ipv6.sh leaves numerous Docker container ports exposed. The affected state requires an OVA deployment with IPv6 enabled, and the documented impact is limited to exposure of listening services.
Summary
What happened
Network exposure in Brocade SANnav before 2.1.1 allows attackers to reach Docker container ports through IPv6 networking. IPv6 configuration during OVA installation or through change-ipv4-installation-to-ipv6.sh leaves numerous Docker container ports exposed. The affected state requires an OVA deployment with IPv6 enabled, and the documented impact is limited to exposure of listening services.
The record
- CVE
- CVE-2020-15378
- Published
- Jun 9, 2021
- Updated
- Aug 4, 2024
- Vendor
- Brocade Communications Systems
- Product
- SANnav
- Classifications
- T1046
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 9, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Brocade SANnav before version 2.1.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo