dbcve.org
Edgeconnect EnterpriseWeb browser · Arubanetworks

CVE-2022-37919

HIGH · 7.5 CVSS v3.1 Published 2022-12-12
Fix available
A fix is available. Upgrade to after 9.2.1.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
A vulnerability exists in the API of Aruba EdgeConnect Enterprise. An unauthenticated attacker can exploit this condition via the web-based management interface to create a denial-of-service condition which prevents the appliance from properly responding to API requests 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

An unauthenticated attacker can exploit a vulnerability in the Aruba EdgeConnect Enterprise API through the web-based management interface to cause a denial-of-service condition, preventing the appliance from responding to API requests. The vulnerability affects multiple ECOS versions up to the specified thresholds.

MitigationUpgrade to a patched ECOS version beyond 9.2.1.0, 9.1.3.0, 9.0.7.0, or 8.3.7.1 as specified in Aruba's security advisory, and consider restricting web management interface access to trusted networks.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Determine installed ECOS version
    Access the EdgeConnect CLI or web management interface and retrieve the system version information. In the CLI, this is typically shown by running 'show version' or similar system information commands. In the web UI, version info is usually displayed in the dashboard or system settings.
    Affected if The installed version falls within any of these ranges: 8.3.1.0 through 8.3.7.1, 9.0.0.0 through 9.0.7.0, 9.1.0.0 through 9.1.3.0, or 9.2.0.0 through 9.2.1.0
  2. Verify web-based management interface is enabled
    Check the EdgeConnect configuration for the web management interface status. This is typically found in the system settings, network configuration, or management access settings within the web UI or CLI.
    Affected if The web-based management interface is enabled and accessible over the network
  3. Confirm API access through web management
    Verify that the REST API functionality is available through the web management interface. This may be confirmed by attempting to access the API endpoint or reviewing the management interface configuration for API enablement status.
    Affected if API access is permitted through the web management interface, allowing unauthenticated requests to reach the API endpoint

If the installed ECOS version is within any of the affected ranges and the web-based management interface with API access is enabled, the environment is vulnerable to the CVE-2022-37919 denial-of-service condition.

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 to a patched ECOS version beyond 9.2.1.0, 9.1.3.0, 9.0.7.0, or 8.3.7.1 as specified in Aruba's security advisory, and consider restricting web management interface access to trusted networks.

Recommended fix Moderate confidence

ECOS 9.2.2.0 or later (or the corresponding fix in your version branch: 8.3.8.0+, 9.0.8.0+, 9.1.4.0+)

  1. 1. Identify the currently installed EdgeConnect Enterprise version via the web-based management interface or CLI (show version command)
  2. 2. Determine the appropriate upgrade path based on your current major version branch (8.3.x, 9.0.x, 9.1.x, or 9.2.x)
  3. 3. Download the fixed ECOS software from the Aruba support portal at https://asp.arubanetworks.com/
  4. 4. Back up the current EdgeConnect configuration via the web UI (System > Backup/Restore) or CLI (backup command)
  5. 5. Upload the new ECOS image via the web UI (System > Software Management > Upload) or TFTP/FTP
  6. 6. Schedule a maintenance window as the upgrade will require a brief system reboot
  7. 7. Install the upgrade and reboot the appliance
  8. 8. After reboot, verify the new version is running and confirm API functionality is restored
Caveat Review Aruba release notes for your target version for any configuration or behavioral changes; some upgrades may require intermediate steps if jumping multiple version branches

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

Fix this in Edgeconnect Enterprise Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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