CVE-2021-26965
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 · uneditedA 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 confidenceAn authenticated SQL injection vulnerability exists in the API of Aruba AirWave Management Platform versions prior to 8.2.12.0. A remote attacker with valid credentials can inject malicious SQL queries through the API endpoints to access or modify sensitive data in the underlying database.
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< 8.2.12.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed AirWave versionAccess the AirWave management console and navigate to Home > AirWave Version or use the command line interface to retrieve the software version (typically via 'show version' or checking /etc/version file on the device).Affected if The installed version is lower than 8.2.12.0
-
Verify API access is enabledCheck the AirWave configuration for API access settings. Typically found under Manage > Users > API Users or in the /mercury_api/ configuration directory. Confirm API endpoints are accessible via HTTP/HTTPS.Affected if API access is enabled and exposed to network users
-
Review API user accountsList all API users in AirWave (usually under Manage > Users or via 'show api-user' command). Identify any accounts with API privileges that may have been created without authorization.Affected if Valid API credentials exist that could be exploited for SQL injection
-
Examine logs for suspicious SQL patternsReview AirWave logs located typically in /var/log/ or via the web interface (Reports > Logs). Search for unusual SQL syntax, UNION SELECT statements, or abnormal database queries associated with API requests.Affected if Logs contain unexpected SQL query patterns or evidence of SQL injection attempts through the API
A user is affected if their AirWave version is below 8.2.12.0 and the API is enabled with valid user credentials that could be exploited for SQL injection.
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 data8.2.12.0
Upgrade Aruba AirWave Management Platform to version 8.2.12.0 or later to remediate this vulnerability. Until upgraded, limit API access to trusted users and monitor for suspicious SQL patterns in logs.
- Consultation8.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-26965 — 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-2021-26965 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