dbcve.org
Extreme Management CenterApplication · Extremenetworks

CVE-2020-16847

MEDIUM · 6.1 CVSS v3.1 Published 2020-08-04
Fix available
A fix is available. Upgrade to 8.5.0.169 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Extreme Analytics in Extreme Management Center before 8.5.0.169 allows unauthenticated reflected XSS via a parameter in a GET request, aka CFD-4887.

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

Reflected cross-site scripting (XSS) vulnerability in Extreme Analytics component of Extreme Management Center versions prior to 8.5.0.169. Unauthenticated attackers can inject malicious JavaScript via a parameter in a GET request, which is reflected back to the victim's browser without proper sanitization.

MitigationUpgrade Extreme Management Center to version 8.5.0.169 or later to patch the vulnerability. Consider implementing WAF rules as a temporary mitigation until the upgrade can be performed.

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
Extreme Management CenterApplication
Affected:< 8.5.0.169

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checks

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

  1. Identify if Extreme Management Center is installed
    Check for the presence of Extreme Management Center on the system by looking for its installation directory, service, or web interface. Common paths may include C:\Program Files\Extreme Networks\Management Center or /opt/ExtremeNetworks/ManagementCenter. Look for the XMC or NetSight service running on the server.
    Affected if Extreme Management Center is not installed on the system.
  2. Determine the installed version of Extreme Management Center
    Access the Extreme Management Center web interface and navigate to the Help or About section, typically found under the gear icon or menu. Alternatively, check the version from the installation files, release notes, or the service information if available locally.
    Affected if The version cannot be determined or is not visible.
  3. Compare the installed version against the affected range
    If the version is visible, compare it to 8.5.0.169. Versions prior to 8.5.0.169 are affected (e.g., 8.5.0.0 through 8.5.0.168, or any version 8.x earlier than the patched release).
    Affected if The installed version is lower than 8.5.0.169.
  4. Check if Extreme Analytics component is enabled
    In the Extreme Management Center web interface, navigate to the Extreme Analytics section (usually under Reports, Analytics, or the dashboard). Verify whether the Extreme Analytics module or reporting feature is active and accessible.
    Affected if Extreme Analytics component is enabled and accessible.
  5. Verify the vulnerable GET request endpoint is reachable
    Attempt to access a typical Extreme Analytics endpoint via HTTP GET request, observing whether the application reflects input parameters back in the response without sanitization. This typically involves submitting a test parameter in the URL and checking the response.
    Affected if The endpoint reflects unsanitized input in the response.

A user is affected if Extreme Management Center is installed with a version lower than 8.5.0.169 and the Extreme Analytics component is enabled, allowing unauthenticated reflected XSS via GET request parameters.

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.

From vendor data
Upgrade available Upgrade to 8.5.0.169 or later
Fixed in 8.5.0.169
Interim mitigation

Upgrade Extreme Management Center to version 8.5.0.169 or later to patch the vulnerability. Consider implementing WAF rules as a temporary mitigation until the upgrade can be performed.

Fix this in Extreme Management Center Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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