CVE-2022-37920
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 · uneditedVulnerabilities 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 confidenceCommand injection vulnerability in Aruba EdgeConnect Enterprise CLI allows remote authenticated users to execute arbitrary commands as root on the underlying operating system, achieving 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>= 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.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
- 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 installed EdgeConnect versionAccess the EdgeConnect CLI or web management interface and run the command to display the system version, typically via 'show version' or checking the web UI dashboard for the firmware/software versionAffected 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
-
Verify CLI service is exposedConfirm whether the EdgeConnect CLI service (typically SSH on port 22 or custom CLI port) is accessible from the network by checking the management interface bindings and firewall rulesAffected if CLI access is enabled and reachable from untrusted network segments
-
Confirm authenticated CLI access existsReview user accounts configured for CLI access and check whether any non-administrator or low-privilege accounts have CLI login permissionsAffected if Any user account with CLI login privileges exists in the system, as the vulnerability allows any authenticated CLI user to execute commands as root
-
Inspect CLI command execution logsReview system logs, CLI audit logs, or shell history for any unexpected or unauthorized command executions, particularly commands run as root or system-level operations not initiated by known administratorsAffected if Logs show CLI commands executed by users who should not have had command execution permissions or commands originating from unexpected sources
Your environment is affected if the installed EdgeConnect Enterprise version falls within any of the affected ranges AND the CLI service is accessible with authenticated user accounts, as the vulnerability allows any CLI-authenticated user to achieve root command execution.
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.
dbcve · scopedApply vendor-provided patches to update EdgeConnect Enterprise to a fixed version beyond the affected releases (9.2.1.0, 9.1.3.0, 9.0.7.0, 8.3.7.1 and below). Restrict CLI access to trusted, least-privilege accounts and implement network segmentation as compensating controls until patching is complete.
Upgrade to ECOS version 8.3.7.2 or later, 9.0.7.1 or later, 9.1.3.1 or later, or 9.2.1.1 or later (depending on your release branch)
- 1. Identify the currently installed EdgeConnect Enterprise version using 'show version' in the CLI
- 2. Access the Aruba support portal at https://asp.arubanetworks.com/ to obtain the latest security patches
- 3. Download the appropriate patch for your version branch (8.3.x, 9.0.x, 9.1.x, or 9.2.x)
- 4. Upload the patch to the EdgeConnect Enterprise appliance via the Web UI or SCP
- 5. Apply the patch using the CLI command 'patch install <filename>'
- 6. Reboot the appliance if required by the patch installation process
- 7. Verify the installation was successful using 'show version' and confirm the patch level
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-37920 — 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-2022-37920 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