dbcve.org
5400r FirmwareOperating system · Arubanetworks

CVE-2019-5322

HIGH · 7.5 CVSS v3.1 Published 2020-02-13
Fix available
A fix is available. Upgrade to 16.08.0009 / 16.09.0007 or later.
See remediation →
84/100
Remediation priority · High
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 remotely exploitable information disclosure vulnerability is present in Aruba Intelligent Edge Switch models 5400, 3810, 2920, 2930, 2530 with GigT port, 2530 10/100 port, or 2540. The vulnerability impacts firmware 16.08.* before 16.08.0009, 16.09.* before 16.09.0007 and 16.10.* before 16.10.0003. The vulnerability allows an attacker to retrieve sensitive system information. This attack can be carried out without user authentication under very specific conditions.

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

This is a remotely exploitable information disclosure vulnerability in Aruba Intelligent Edge Switches (models 5400, 3810, 2920, 2930, 2530, and 2540) that allows unauthenticated attackers to retrieve sensitive system information under specific conditions in affected firmware versions (16.08.x before 16.08.0009, 16.09.x before 16.09.0007, and 16.10.x before 16.10.0003).

MitigationUpgrade affected switch firmware to version 16.08.0009, 16.09.0007, or 16.10.0003 or later as appropriate for your model. If immediate patching is not feasible, restrict network access to the management interfaces to limit attack surface.

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 With Gigt Port FirmwareOperating system
Affected:>= 16.08.0, < 16.08.0009>= 16.09.0, < 16.09.0007>= 16.10.0, < 16.10.0003
2530 10\/100 Port 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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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
    Access the switch CLI or web interface and run 'show system information' or check the device label to confirm the model number (5400, 3810, 2920, 2930, 2530, or 2540)
    Affected if The model is NOT one of these six affected models - you are not affected
  2. Determine the firmware version
    Run 'show version' in the switch CLI or check the firmware version displayed in the web interface
    Affected if Version is not displayed or cannot be retrieved - manual verification required
  3. Compare version to affected ranges
    Check if the installed firmware falls within: 16.08.0 to 16.08.0008 (inclusive), 16.09.0 to 16.09.0006 (inclusive), or 16.10.0 to 16.10.0002 (inclusive)
    Affected if The version is within any of these ranges - you are likely affected by this CVE
  4. Verify management interface exposure
    Confirm whether the switch management interface (HTTP/HTTPS, SNMP, telnet) is accessible from untrusted networks by reviewing firewall rules, VLAN configs, and ACLs
    Affected if Management interfaces are exposed to untrusted networks without restrictive ACLs - exploitation is possible

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 affected switch firmware to version 16.08.0009, 16.09.0007, or 16.10.0003 or later as appropriate for your model. If immediate patching is not feasible, restrict network access to the management interfaces to limit attack surface.

Fix this in 5400r Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
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,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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