CVE-2019-5321
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 · uneditedAruba 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 Remote Unauthorized Access in the WebUI.
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 confidenceRemote unauthorized access vulnerability in the WebUI of Aruba Intelligent Edge Switch Series 2540, 2530, 2930F, 2930M, 2920, 5400R, and 3810M with firmware versions prior to 16.08.0009, 16.09.0007, or 16.10.0003. An attacker could exploit this to gain unauthorized access to the switch management interface.
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>= 16.08.0, < 16.08.0009>= 16.09.0, < 16.09.0007>= 16.10.0, < 16.10.0003>= 16.08.0, < 16.08.0009>= 16.09.0, < 16.09.0007>= 16.10.0, < 16.10.0003>= 16.08.0, < 16.08.0009>= 16.09.0, < 16.09.0007>= 16.10.0, < 16.10.0003>= 16.08.0, < 16.08.0009>= 16.09.0, < 16.09.0007>= 16.10.0, < 16.10.0003>= 16.08.0, < 16.08.0009>= 16.09.0, < 16.09.0007>= 16.10.0, < 16.10.0003>= 16.08.0, < 16.08.0009>= 16.09.0, < 16.09.0007>= 16.10.0, < 16.10.0003CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify your Aruba switch modelLog into the switch CLI and run 'show system-information' or check the physical label to confirm the model is one of: 2540, 2530, 2930F, 2930M, 2920, 5400R, or 3810MAffected if The switch model is NOT one of the listed affected series
-
Check the installed firmware versionLog into the switch CLI and run 'show version' or 'show flash' to display the firmware versionAffected if The switch model is one of the affected series AND the firmware version falls within the affected ranges (16.08.0 to <16.08.0009, 16.09.0 to <16.09.0007, or 16.10.0 to <16.10.0003)
-
Determine if the WebUI is enabledRun 'show web-management' in the switch CLI to check if the WebUI feature is currently enabledAffected if WebUI is enabled on the switch (the vulnerability only affects switches with WebUI active)
-
Assess WebUI network exposureCheck the management VLAN configuration and access lists with 'show management' and 'show access-list' to see if the WebUI interface is reachable from untrusted networksAffected if The WebUI is accessible from outside trusted management networks
You are affected if you have an Aruba 2540, 2530, 2930F, 2930M, 2920, 5400R, or 3810M switch running firmware version 16.08.0-16.08.0008, 16.09.0-16.09.0006, or 16.10.0-16.10.0002 with the WebUI enabled and accessible.
Generated from the published advisory. Verify against your own configuration.
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 data16.08.000916.09.000716.10.0003
Update firmware to version 16.08.0009, 16.09.0007, 16.10.0003 or later. Restrict WebUI access to trusted networks or disable it if not needed.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5321 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-5321 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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