Aruba InstantHardware / appliance · Aruba

CVE-2021-34618

MEDIUM · 6.5 CVSS v3.1 Published 2021-07-19
Fix available
A fix is available. Upgrade to after 8.7.1.1 or later.
See remediation →
70/100
Remediation priority · Elevated
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 remote denial of service (DoS) vulnerability was discovered in some Aruba Instant Access Point (IAP) products in version(s): Aruba Instant 6.4.x: 6.4.4.8-4.2.4.18 and below; Aruba Instant 6.5.x: 6.5.4.18 and below; Aruba Instant 8.3.x: 8.3.0.14 and below; Aruba Instant 8.4.x: All versions; Aruba Instant 8.5.x: 8.5.0.11 and below; Aruba Instant 8.6.x: 8.6.0.7 and below; Aruba Instant 8.7.x: 8.7.1.1 and below. Aruba has released patches for Aruba Instant 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 · high confidence

A remote denial of service vulnerability exists in Aruba Instant Access Point (IAP) products across multiple version branches (6.4.x through 8.7.x). An unauthenticated remote attacker can exploit this to cause the affected AP to become unavailable, disrupting wireless network services.

MitigationApply the appropriate Aruba Instant firmware patches for the specific version branch in use, as released by Aruba. Prioritize updating 8.4.x versions which are affected across all versions.

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
Aruba InstantHardware / appliance
Affected:>= 6.4.0, <= 6.4.4.8-4.2.4.18>= 6.5.0, <= 6.5.4.18>= 8.3.0, <= 8.3.0.14>= 8.4.0, <= 8.5.0.11>= 8.6.0, <= 8.6.0.7>= 8.7.0, <= 8.7.1.1

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/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. Identify the Aruba Instant AP model
    Access the Aruba Instant WebUI or CLI and locate the device model information, typically shown on the Dashboard or in the Maintenance > System > Summary page
    Affected if The device is an Aruba IAP model (such as IAP-200 series, IAP-300 series, or newer Instant APs)
  2. Retrieve the installed Aruba Instant firmware version
    In the WebUI, go to Maintenance > System > Summary or use the CLI command 'show version' to display the running firmware version
    Affected if The displayed version cannot be retrieved or the device is unresponsive due to the DoS condition
  3. Compare the firmware version against affected ranges
    Check if the installed version falls within any of these ranges: 6.4.0-6.4.4.x, 6.5.0-6.5.4.x, 8.3.0-8.3.0.x, 8.4.0-8.5.0.x, 8.6.0-8.6.0.x, or 8.7.0-8.7.1.x
    Affected if The installed version number is within any of the listed version ranges, indicating the device is vulnerable to the DoS attack
  4. Verify if the device has become unavailable
    Attempt to access the WebUI or CLI, or check if wireless clients can connect to SSIDs broadcast by the AP
    Affected if The AP is unresponsive or wireless services are disrupted, confirming active exploitation

If the Aruba Instant AP is running a firmware version within the 6.4.x through 8.7.1.x range and is currently available, it is likely affected by this vulnerability and could be targeted for remote DoS.

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 a release after 8.7.1.1
Interim mitigation

Apply the appropriate Aruba Instant firmware patches for the specific version branch in use, as released by Aruba. Prioritize updating 8.4.x versions which are affected across all versions.

Fix this in Aruba Instant Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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