dbcve.org
5400r FirmwareOperating system · Arubanetworks

CVE-2019-5320

MEDIUM · 6.1 CVSS v3.1 Published 2020-08-26
Fix available
A fix is available. Upgrade to 16.08.0009 / 16.09.0007 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
Aruba Intelligent Edge Switch Series 2540, 2530, 2930F, 2930M, 2920, 5400R, and 3810M with firmware 16.08.* before 16.08.0009, 16.09.* before 16.09.0007, 16.10.* before 16.10.0003 are vulnerable to Cross Site Scripting in the web UI, leading to injection of code.

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

Cross Site Scripting (XSS) vulnerability in the web UI of Aruba Intelligent Edge Switch Series 2540, 2530, 2930F, 2930M, 2920, 5400R, and 3810M with firmware versions 16.08.* before 16.08.0009, 16.09.* before 16.09.0007, and 16.10.* before 16.10.0003 allows injection of malicious script code through the web interface.

MitigationUpgrade firmware to version 16.08.0009, 16.09.0007, or 16.10.0003 or later per the Aruba security advisory.

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
5400r FirmwareOperating system
Affected:>= 16.08.0, < 16.08.0009>= 16.09.0, < 16.09.0007>= 16.10.0, < 16.10.0003
3810 FirmwareOperating system
Affected:>= 16.08.0, < 16.08.0009>= 16.09.0, < 16.09.0007>= 16.10.0, < 16.10.0003
2920 FirmwareOperating system
Affected:>= 16.08.0, < 16.08.0009>= 16.09.0, < 16.09.0007>= 16.10.0, < 16.10.0003
2930 FirmwareOperating system
Affected:>= 16.08.0, < 16.08.0009>= 16.09.0, < 16.09.0007>= 16.10.0, < 16.10.0003
2530 FirmwareOperating system
Affected:>= 16.08.0, < 16.08.0009>= 16.09.0, < 16.09.0007>= 16.10.0, < 16.10.0003
2540 FirmwareOperating system
Affected:>= 16.08.0, < 16.08.0009>= 16.09.0, < 16.09.0007>= 16.10.0, < 16.10.0003

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 the switch model
    Run 'show version' or 'show system information' via CLI to identify whether the device is one of these models: 2540, 2530, 2930F, 2930M, 2920, 5400R, or 3810M
    Affected if The device model is not in the affected product list (2540, 2530, 2930F, 2930M, 2920, 5400R, 3810M)
  2. Determine the installed firmware version
    Run 'show version' via CLI and locate the firmware version string (for example, 16.08.0005 or 16.10.0001)
    Affected if The firmware version falls within any of these ranges: >= 16.08.0 and < 16.08.0009, OR >= 16.09.0 and < 16.09.0007, OR >= 16.10.0 and < 16.10.0003
  3. Verify if the web UI is enabled
    Run 'show web-management' via CLI to check whether the web-based management interface is currently enabled
    Affected if The web UI is enabled and the firmware version is in any of the affected ranges listed above

The environment is affected if the device is a model 2540, 2530, 2930F, 2930M, 2920, 5400R, or 3810M with a vulnerable firmware version (16.08.x before 16.08.0009, 16.09.x before 16.09.0007, or 16.10.x before 16.10.0003) and the web UI is enabled.

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 16.08.0009 / 16.09.0007 / 16.10.0003 or later
Fixed in 16.08.000916.09.000716.10.0003
Interim mitigation

Upgrade firmware to version 16.08.0009, 16.09.0007, or 16.10.0003 or later per the Aruba security advisory.

Fix this in 5400r Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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