AirwaveApplication · Arubanetworks

CVE-2021-26966

MEDIUM · 6.5 CVSS v3.1 Published 2021-03-05
Fix available
A fix is available. Upgrade to 8.2.12.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 authenticated sql injection vulnerability was discovered in Aruba AirWave Management Platform version(s): Prior to 8.2.12.0. Multiple vulnerabilities in the API of AirWave could allow an authenticated remote attacker to conduct SQL injection attacks against the AirWave instance. An attacker could exploit these vulnerabilities to obtain and modify sensitive information in the underlying database.

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

SQL injection vulnerability in the API of Aruba AirWave Management Platform allows authenticated remote attackers to inject malicious SQL queries. Exploitation enables attackers to retrieve or modify sensitive data stored in the underlying database.

MitigationUpgrade to AirWave version 8.2.12.0 or later. If immediate patching is not feasible, restrict API access to trusted IP addresses and implement logging to detect SQL injection attempts.

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
AirwaveApplication
Affected:< 8.2.12.0

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 AirWave installation
    Locate the AirWave installation directory and locate the version file. Common paths include /var/airwave or /opt/airwave. Look for a VERSION file or check the web interface login page for the version number.
    Affected if AirWave software is present on the system
  2. Verify installed version
    Compare your AirWave version to the affected range. Versions prior to 8.2.12.0 are vulnerable. Check the version displayed in the web UI footer or via CLI command 'airwave version' if available.
    Affected if Installed version is lower than 8.2.12.0
  3. Confirm API accessibility
    Determine if the AirWave API endpoint is exposed. Check network configuration to see if API ports (typically 443/https) are accessible from untrusted networks. Review firewall rules and reverse proxy configurations.
    Affected if API port is reachable from untrusted network segments
  4. Check API authentication status
    Review AirWave user accounts that have API access. Examine whether default or weak credentials exist, and check if API keys or tokens are improperly stored or transmitted.
    Affected if API is accessible with valid authentication credentials
  5. Review API access logs
    Inspect AirWave logs for suspicious API requests containing SQL injection patterns such as single quotes, UNION SELECT, OR 1=1, or other SQL syntax in parameters.
    Affected if Logs show SQL injection attempt patterns in API requests

The environment is affected if AirWave version is lower than 8.2.12.0 AND the API is accessible from a network where untrusted attackers can obtain valid authentication credentials.

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 8.2.12.0 or later
Fixed in 8.2.12.0
Interim mitigation

Upgrade to AirWave version 8.2.12.0 or later. If immediate patching is not feasible, restrict API access to trusted IP addresses and implement logging to detect SQL injection attempts.

Fix this in Airwave Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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