dbcve.org
Edgeconnect EnterpriseWeb browser · Arubanetworks

CVE-2022-37921

HIGH · 7.2 CVSS v3.1 Published 2022-12-12
Fix available
A fix is available. Upgrade to after 9.2.1.0 or later.
See remediation →
78/100
Remediation priority · High
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
Vulnerabilities in the Aruba EdgeConnect Enterprise command line interface allow remote authenticated users to run arbitrary commands on the underlying host. A successful exploit could allow an attacker to execute arbitrary commands as root on the underlying operating system leading to complete system compromise in Aruba EdgeConnect Enterprise Software version(s): ECOS 9.2.1.0 and below; ECOS 9.1.3.0 and below; ECOS 9.0.7.0 and below; ECOS 8.3.7.1 and below.

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

Authenticated command injection vulnerabilities in the Aruba EdgeConnect Enterprise CLI allow remote attackers with valid credentials to execute arbitrary commands as root on the underlying operating system, leading to complete system compromise.

MitigationApply vendor-supplied patches or upgrade to a fixed ECOS version beyond the affected versions (9.2.1.0, 9.1.3.0, 9.0.7.0, 8.3.7.1) for all affected EdgeConnect Enterprise installations.

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
Edgeconnect EnterpriseWeb browser
Affected:>= 8.3.1.0, <= 8.3.7.1>= 9.0.0.0, <= 9.0.7.0>= 9.1.0.0, <= 9.1.3.0>= 9.2.0.0, <= 9.2.1.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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify EdgeConnect Enterprise installation
    Locate Aruba EdgeConnect Enterprise appliances in your environment by checking system inventory, network documentation, or by accessing the device via SSH or console
    Affected if The target system is running Arubanetworks EdgeConnect Enterprise software
  2. Determine ECOS version
    Log into the EdgeConnect CLI and run the command to display the system version, typically 'show version' or 'system info' command, or check the boot console output
    Affected if The displayed ECOS version matches one of the affected ranges: 8.3.1.0-8.3.7.1, 9.0.0.0-9.0.7.0, 9.1.0.0-9.1.3.0, or 9.2.0.0-9.2.1.0
  3. Verify CLI access method
    Confirm that the CLI is accessible via SSH or console connection with valid user credentials
    Affected if Remote CLI authentication is enabled and reachable on the EdgeConnect appliance

A user is affected if they are running any EdgeConnect Enterprise version within the four affected ranges AND the CLI is accessible with valid credentials, allowing authenticated command injection as root.

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

Apply vendor-supplied patches or upgrade to a fixed ECOS version beyond the affected versions (9.2.1.0, 9.1.3.0, 9.0.7.0, 8.3.7.1) for all affected EdgeConnect Enterprise installations.

Recommended fix High confidence

Upgrade to ECOS 8.3.7.2 or later (8.x branch), 9.0.8.0 or later (9.0.x branch), 9.1.4.0 or later (9.1.x branch), or 9.2.2.0 or later (9.2.x branch)

  1. Identify the currently installed EdgeConnect Enterprise version using the CLI command 'show version' or through the web interface
  2. Determine which software branch (8.x, 9.0.x, 9.1.x, or 9.2.x) is currently in use
  3. Download the appropriate fixed release for your branch from the Aruba support portal: For 8.3.x branch: upgrade to 8.3.7.2 or later; For 9.0.x branch: upgrade to 9.0.8.0 or later; For 9.1.x branch: upgrade to 9.1.4.0 or later; For 9.2.x branch: upgrade to 9.2.2.0 or later
  4. Upload the new software image to the EdgeConnect appliance via SCP or through the web UI (System > Software Update > Upload)
  5. Schedule a maintenance window as the upgrade will require a system reboot
  6. Initiate the upgrade from the CLI using 'software upload <filename>' followed by 'software activate <filename>' or via the web UI
  7. After the device reboots, verify the new version is running with 'show version'
  8. Verify the CLI restricted shell is properly enforcing command authorization for non-privileged users
Caveat Standard upgrade downtime required; ensure proper maintenance window is scheduled; backup configuration before upgrade

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

Fix this in Edgeconnect Enterprise Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-37921 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2022-37921 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