dbcve.org
SannavApplication · Broadcom

CVE-2020-15377

CRITICAL · 9.8 CVSS v3.1 Published 2021-06-09
Fix available
A fix is available. Upgrade to 2.1.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Webtools in Brocade SANnav before version 2.1.1 allows unauthenticated users to make requests to arbitrary hosts due to a misconfiguration; this is commonly referred to as Server-Side Request Forgery (SSRF).

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 confidence

Server-Side Request Forgery (SSRF) vulnerability in Brocade SANnav webtools allows unauthenticated remote attackers to trick the application into making HTTP requests to arbitrary hosts due to a misconfiguration. This can be exploited to scan internal networks, access internal services, or bypass firewalls.

MitigationUpgrade Brocade SANnav to version 2.1.1 or later. If immediate upgrade is not possible, restrict network access to the management interface and monitor for suspicious outbound requests.

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
SannavApplication
Affected:< 2.1.1

CVSS 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Brocade SANnav is installed
    Locate the SANnav installation directory or check running processes for SANnav components. Typical paths may include /opt/sannav or similar installation directories. Look for Java processes running the SANnav web application.
    Affected if Brocade SANnav software is found running on the system
  2. Identify the installed SANnav version
    Access the SANnav web interface and navigate to the About or Help section to view the version number. Alternatively, check installation logs or version files within the SANnav installation directory.
    Affected if The installed version is lower than 2.1.1 (e.g., 2.0.x, 1.x.x)
  3. Verify webtools component is accessible
    Attempt to access the webtools endpoint via HTTP/HTTPS on the SANnav management port (typically 8080 or 8443). Check if the /webtools path responds.
    Affected if The webtools interface is reachable over the network without authentication
  4. Check network exposure of management interface
    Review firewall rules or network access control lists to determine if the SANnav web interface (including webtools) is exposed to untrusted networks or the public internet.
    Affected if The management interface is accessible from untrusted networks or the internet
  5. Review outbound HTTP traffic logs
    Examine SANnav server logs and network firewall logs for suspicious outbound HTTP/HTTPS requests to internal IP addresses, private network ranges, or unusual destinations that were initiated by the SANnav application.
    Affected if Logs show unexpected outbound requests originating from the SANnav server to internal or arbitrary hosts

A user is affected if Broadcom SANnav version lower than 2.1.1 is installed AND the webtools component is accessible over the network, allowing unauthenticated attackers to trigger arbitrary HTTP requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 2.1.1 or later
Fixed in 2.1.1
Interim mitigation

Upgrade Brocade SANnav to version 2.1.1 or later. If immediate upgrade is not possible, restrict network access to the management interface and monitor for suspicious outbound requests.

Recommended fix Moderate confidence

SANnav version 2.1.1 or later

  1. Back up the current SANnav configuration and any critical data before upgrading
  2. Download SANnav version 2.1.1 or later from the official Broadcom support portal at www.broadcom.com
  3. Review Broadcom's official upgrade documentation for SANnav to ensure compatibility with your environment
  4. Execute the upgrade following the documented upgrade procedure for your deployment type (virtual appliance or physical)
  5. After upgrade completes, verify the Webtools component is running the fixed version
  6. Confirm the SSRF vulnerability is remediated by attempting to validate that unauthenticated requests to arbitrary hosts are no longer possible
Caveat Review upgrade documentation for any compatibility requirements or migration steps specific to your deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sannav Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-15377 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-15377 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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