CVE-2022-37922
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 authenticated remote attackers to execute arbitrary commands as root on the underlying operating system, leading to complete system compromise. The flaw bypasses normal command restrictions in the CLI interface.
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 the EdgeConnect ECOS versionLog into the EdgeConnect CLI or management interface and retrieve the running ECOS version using the command 'show version' or equivalent version display commandAffected if The installed version falls within 8.3.1.0 to 8.3.7.1, 9.0.0.0 to 9.0.7.0, 9.1.0.0 to 9.1.3.0, or 9.2.0.0 to 9.2.1.0
-
Confirm CLI service is exposedCheck if the CLI management service is accessible from network segments outside the trusted administrator zone. Review firewall rules or access control lists that govern inbound access to TCP port 22 (SSH) or other CLI access portsAffected if CLI access is permitted from untrusted networks or the internet
-
Audit CLI user accountsReview the list of configured CLI users and administrators using 'show users' or equivalent command in the EdgeConnect CLIAffected if Unexpected or unauthorized user accounts exist in the system
-
Examine CLI command logsInspect CLI audit logs or session logs for any commands that deviate from normal administrative operations, looking for suspicious command patterns or unexpected command executionsAffected if Logs contain commands that appear to execute operating system operations outside the expected CLI command set, or show commands executed by users without proper authorization
The environment is affected if the EdgeConnect ECOS version falls within any of the affected ranges AND the CLI interface is accessible to an authenticated attacker (whether legitimate credentials are compromised or unauthorized accounts exist).
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 patches for affected ECOS versions (9.2.1.0 and below, 9.1.3.0 and below, 9.0.7.0 and below, 8.3.7.1 and below). Restrict CLI access to trusted administrators and apply network segmentation to limit exposure until patches are applied.
Upgrade to ECOS 9.2.2.0 or later (or the latest available stable release beyond 9.2.1.0)
- Contact Aruba Networks or check Aruba support portal for the specific hotfix/patch for CVE-2022-37922
- Alternatively, upgrade to a version newer than ECOS 9.2.1.0 (e.g., 9.2.2.0 or later) which should contain the fix
- Before upgrading, review release notes to confirm the version includes the security fix for this vulnerability
- Plan maintenance window for upgrade procedure
- After upgrade, verify the CLI command injection vulnerability is resolved
- Limit CLI access to trusted admin users only as an additional security measure
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.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,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-37922 — 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-37922 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