CVE-2020-24638
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 · uneditedMultiple authenticated remote command executions are possible in Airwave Glass before 1.3.3 via the glassadmin cli. These allow for a user with glassadmin privileges to execute arbitrary code as root on the underlying host operating system.
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 confidenceAirwave Glass versions before 1.3.3 contain multiple authenticated remote command execution vulnerabilities in the glassadmin command-line interface. An authenticated user with glassadmin privileges can execute arbitrary code as root on the underlying host operating system, resulting in complete system compromise.
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< 1.3.3CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Airwave Glass is deployedCheck your systems for the presence of Arubanetworks Airwave Glass software. This is typically installed on dedicated hardware or as a virtual appliance. Look for the glassadmin CLI tool in the system PATH or installation directory.Affected if Airwave Glass is installed and running on the system
-
Determine the installed Airwave Glass versionRun 'glassadmin version' or check the software version through the management interface. Compare your version number to the affected range of versions before 1.3.3.Affected if The installed version is lower than 1.3.3 (for example, 1.3.0, 1.2.x, or earlier)
-
Verify glassadmin CLI accessibilityConfirm that the glassadmin command-line interface is accessible on the Airwave Glass appliance. Check if the glassadmin binary exists and responds to commands.Affected if The glassadmin CLI is present and functional on the system
-
Audit glassadmin user accessReview the list of users who have glassadmin privileges granted to them. Check authentication logs or user configuration for accounts with glassadmin role.Affected if There are any user accounts with glassadmin privileges configured
You are affected if Airwave Glass is installed with a version lower than 1.3.3 and the glassadmin CLI is accessible with authenticated user accounts.
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 data1.3.3
Upgrade Airwave Glass to version 1.3.3 or later to remediate these vulnerabilities. Until then, restrict glassadmin access to only trusted administrators and monitor for suspicious CLI activity.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24638 — 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-2020-24638 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