ArubaosOperating system · Arubanetworks

CVE-2019-5318

MEDIUM · 6.5 CVSS v3.1 Published 2021-09-07
Fix available
A fix is available. Upgrade to 8.8.0.0 or later.
See remediation →
72/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
A remote cross-site request forgery (csrf) vulnerability was discovered in Aruba Operating System Software version(s): 6.x.x.x: all versions, 8.x.x.x: all versions prior to 8.8.0.0. Aruba has released patches for ArubaOS that address this security vulnerability.

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 remote cross-site request forgery (CSRF) vulnerability in ArubaOS allows attackers to trick authenticated users into unknowingly executing unintended actions. The vulnerability affects all versions of ArubaOS 6.x and versions prior to 8.8.0.0 in the 8.x branch.

MitigationApply the Aruba-provided patches by upgrading to ArubaOS 8.8.0.0 or later, or obtain the appropriate vendor patch for version 6.x.

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
ArubaosOperating system
Affected:>= 6.1.3.7, <= 6.5.4.20>= 8.0.0.0, < 8.8.0.0
Scalance W1750d FirmwareOperating system
Affected:all versions

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
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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. Check ArubaOS version via CLI
    Log into the Aruba device and run the command 'show version' or 'show system information' to retrieve the installed ArubaOS version number.
    Affected if The version displayed falls within 6.1.3.7 to 6.5.4.20, or 8.0.0.0 to any version before 8.8.0.0.
  2. Check ArubaOS version via web interface
    Access the Aruba controller web management interface and navigate to the Dashboard or About page to view the firmware version.
    Affected if The version displayed falls within 6.1.3.7 to 6.5.4.20, or 8.0.0.0 to any version before 8.8.0.0.
  3. Verify Siemens Scalance W1750d firmware version
    Access the Scalance W1750d web interface or use the device's management console to retrieve the firmware version information.
    Affected if Any firmware version is installed, as all versions of this product are affected.
  4. Confirm active management interface
    Check if the web-based management interface or CLI is accessible and in use by viewing the device status or active services.
    Affected if The device has an active management web interface, which is required for the CSRF attack vector to be exploitable.

You are affected if your ArubaOS version is 6.1.3.7 through 6.5.4.20, or 8.0.0.0 through any version before 8.8.0.0, or if you use any version of Siemens Scalance W1750d firmware with the web management interface 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.

dbcve · scoped
Upgrade available Upgrade to 8.8.0.0 or later
Fixed in 8.8.0.0
Interim mitigation

Apply the Aruba-provided patches by upgrading to ArubaOS 8.8.0.0 or later, or obtain the appropriate vendor patch for version 6.x.

Recommended fix Moderate confidence

ArubaOS 8.8.0.0 or later (or appropriate patched release for 6.x branch from Aruba support)

  1. Upgrade ArubaOS 8.x to version 8.8.0.0 or later
  2. For ArubaOS 6.x, apply the appropriate patch from Aruba's support portal for your specific 6.x version
  3. After upgrading, verify the CSRF protection is functioning by reviewing the device configuration
  4. For Scalance W1750d, contact Siemens for available firmware updates addressing this vulnerability
Caveat Review Aruba upgrade instructions for your specific model; ensure backup of configuration before upgrade

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

Fix this in Arubaos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing8.0 h
  • Review / QA2.0 h
17.0 hours of engineering $2,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-5318 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