dbcve.org
Brocade Network AdvisorApplication · Broadcom

CVE-2016-8204

CRITICAL · 9.8 CVSS v3.1 Published 2017-01-14
Fix available
A fix is available. Upgrade to after 14.0.2 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
A Directory Traversal vulnerability in FileReceiveServlet in the Brocade Network Advisor versions released prior to and including 14.0.2 could allow remote attackers to upload a malicious file in a section of the file system where it can be executed.

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 · moderate confidence

A directory traversal vulnerability in FileReceiveServlet of Brocade Network Advisor allows remote unauthenticated attackers to upload files to arbitrary locations in the file system via path traversal sequences (e.g., '../'), potentially placing executable malicious files in web-accessible directories for remote code execution.

MitigationUpgrade Brocade Network Advisor to a version beyond 14.0.2. If immediate patching is not possible, restrict network access to the FileReceiveServlet endpoint and implement WAF rules to block directory traversal patterns in file upload 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
Brocade Network AdvisorApplication
Affected:<= 14.0.2

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. Identify if Brocade Network Advisor is installed
    Check for running processes or installed services named 'Brocade Network Advisor' or 'BNA', or look for its installation directory in typical application locations
    Affected if Brocade Network Advisor software is present on the system
  2. Determine the installed version
    Check the installed version of Brocade Network Advisor (typically available in the application itself, installation logs, or system registry) and compare it to the affected range <= 14.0.2
    Affected if The installed version is 14.0.2 or any earlier version
  3. Verify if FileReceiveServlet is accessible
    Attempt to access the FileReceiveServlet endpoint (typically at a path containing 'FileReceiveServlet' in the web application's URL structure)
    Affected if The FileReceiveServlet endpoint responds to requests, indicating it is exposed
  4. Check if file upload functionality is enabled
    Inspect whether the web interface or API accepts file upload requests to the FileReceiveServlet path
    Affected if File uploads can be submitted to the FileReceiveServlet without authentication

You are affected if Brocade Network Advisor version 14.0.2 or lower is installed and the FileReceiveServlet is accessible for file uploads.

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 a release after 14.0.2
Interim mitigation

Upgrade Brocade Network Advisor to a version beyond 14.0.2. If immediate patching is not possible, restrict network access to the FileReceiveServlet endpoint and implement WAF rules to block directory traversal patterns in file upload requests.

Recommended fix Moderate confidence

Latest version of Brocade Network Advisor (contact HPE/Broadcom support for exact version number)

  1. 1. Identify the current installed version of Brocade Network Advisor by accessing the application or checking the installation.
  2. 2. Download the latest version of Brocade Network Advisor from the official HPE or Broadcom support portal.
  3. 3. Review the release notes for the latest version to confirm it includes a fix for CVE-2016-8204 (directory traversal in FileReceiveServlet).
  4. 4. Before upgrading, perform a complete backup of the current configuration and database.
  5. 5. Stop the Brocade Network Advisor service following the vendor's recommended procedure.
  6. 6. Install the upgraded version of Brocade Network Advisor.
  7. 7. After installation, verify the FileReceiveServlet has been updated and the path traversal vulnerability is remediated.
  8. 8. Restart the Brocade Network Advisor service.
Caveat Review compatibility notes for your specific environment; ensure backup before upgrade

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

Fix this in Brocade Network Advisor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-8204 — 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-2016-8204 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