dbcve.org
Edgeconnect EnterpriseWeb browser · Arubanetworks

CVE-2022-37923

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

Aruba EdgeConnect Enterprise CLI contains command injection vulnerabilities allowing remote authenticated attackers to execute arbitrary commands as root on the underlying operating system, resulting in complete system compromise.

MitigationUpgrade Aruba EdgeConnect Enterprise to a patched version above the affected releases (ECOS 9.2.1.0, 9.1.3.0, 9.0.7.0, and 8.3.7.1). If immediate patching is not possible, restrict CLI access to trusted management networks and enforce strong authentication.

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 the product and version
    Access the CLI or management interface and run: show version or show system info. Alternatively, check the web UI dashboard for the ECOS version.
    Affected if The displayed version falls within 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.
  2. Confirm CLI access is enabled
    Check if the command-line interface is accessible via SSH, console, or mgmt interface. Run: show cli status or check access settings in the web UI under System > Administration > CLI Access.
    Affected if CLI access is enabled and reachable from any network accessible to untrusted users.
  3. Verify authentication configuration
    Check user accounts and authentication settings: show user or show authentication. Review whether local accounts, RADIUS, or TACACS+ are configured.
    Affected if Valid user credentials exist or can be obtained, allowing authenticated CLI access.
  4. Check management network exposure
    Review firewall rules or access lists: show ip access-list or check the management interface binding. Look for any permitted external networks.
    Affected if CLI is accessible from networks beyond trusted management subnets.

If the EdgeConnect Enterprise version is within the affected ranges AND the CLI is accessible with valid authentication from an untrusted network, the environment is vulnerable to remote command injection.

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

Upgrade Aruba EdgeConnect Enterprise to a patched version above the affected releases (ECOS 9.2.1.0, 9.1.3.0, 9.0.7.0, and 8.3.7.1). If immediate patching is not possible, restrict CLI access to trusted management networks and enforce strong authentication.

Recommended fix Moderate confidence

ECOS 8.3.7.2 or later (8.3.x); ECOS 9.0.8.0 or later (9.0.x); ECOS 9.1.4.0 or later (9.1.x); ECOS 9.2.2.0 or later (9.2.x)

  1. 1. Identify the current ECOS version installed on the Aruba EdgeConnect Enterprise appliance
  2. 2. Determine which version branch (8.3.x, 9.0.x, 9.1.x, or 9.2.x) the current installation belongs to
  3. 3. For version 8.3.x: Upgrade to version 8.3.7.2 or later
  4. 4. For version 9.0.x: Upgrade to version 9.0.8.0 or later
  5. 5. For version 9.1.x: Upgrade to version 9.1.4.0 or later
  6. 6. For version 9.2.x: Upgrade to version 9.2.2.0 or later
  7. 7. Before upgrading, backup the current configuration
  8. 8. Schedule a maintenance window as the upgrade may require service interruption
Caveat Review Aruba release notes for specific version upgrade path as minor version upgrades may have configuration or compatibility considerations

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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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