Aruba Edgeconnect Enterprise OrchestratorWeb browser · Arubanetworks

CVE-2022-37915

CRITICAL · 9.8 CVSS v3.1 Published 2022-10-28
Fix available
A fix is available. Upgrade to 9.1.3.40197 or later.
See remediation →
100/100
Remediation priority · Urgent
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 in the web-based management interface of Aruba EdgeConnect Enterprise Orchestrator could allow an unauthenticated remote attacker to run arbitrary commands on the underlying host. Successful exploitation of this vulnerability could allow an attacker to execute arbitrary commands on the underlying operating system leading to a complete system compromise of Aruba EdgeConnect Enterprise Orchestration with versions 9.1.x branch only, Any 9.1.x Orchestrator instantiated as a new machine with a release prior to 9.1.3.40197, Orchestrators upgraded to 9.1.x were not affected.

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

Unauthenticated command injection vulnerability in the web-based management interface of Aruba EdgeConnect Enterprise Orchestrator allows remote attackers to execute arbitrary OS commands, achieving full system compromise. Affects only NEW machine instantiations of version 9.1.x prior to release 9.1.3.40197; upgraded systems are not affected.

MitigationUpgrade Aruba EdgeConnect Enterprise Orchestrator to version 9.1.3.40197 or later. Until patched, restrict network access to the management interface to reduce exposure.

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
Aruba Edgeconnect Enterprise OrchestratorWeb browser
Affected:>= 9.1.0, < 9.1.3.40197

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Determine installation type
    Check whether the current installation is a NEW machine instantiation or an upgraded system from a prior version. Review deployment documentation, installation logs, or the Orchestrator's system information page for the installation method.
    Affected if The system was deployed as a new machine instantiation (not upgraded from a previous version)
  2. Identify installed version
    Access the Aruba EdgeConnect Enterprise Orchestrator web-based management interface or run the command 'show version' via CLI to retrieve the exact software version number.
    Affected if The installed version is 9.1.0 through 9.1.3.40196 (any version >= 9.1.0 but < 9.1.3.40197)
  3. Verify management interface exposure
    Confirm whether the web-based management interface is accessible from network locations. Check the interface binding configuration and firewall rules controlling access to the management port (default HTTPS port 443).
    Affected if The web-based management interface is reachable from untrusted networks
  4. Check for unauthorized access indicators
    Review Orchestrator audit logs, system logs, and authentication logs for suspicious commands, unexpected administrative actions, or unfamiliar user accounts created around the time of deployment.
    Affected if Logs show unauthorized command execution or unexpected system changes

You are affected if this is a new machine instantiation (not an upgrade) running version 9.1.0 through 9.1.3.40196 with the web management interface exposed to the network.

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 9.1.3.40197 or later
Fixed in 9.1.3.40197
Interim mitigation

Upgrade Aruba EdgeConnect Enterprise Orchestrator to version 9.1.3.40197 or later. Until patched, restrict network access to the management interface to reduce exposure.

Recommended fix High confidence

9.1.3.40197 or later in the 9.1.x branch

  1. 1. Backup the current Aruba EdgeConnect Enterprise Orchestrator configuration before starting the upgrade process
  2. 2. Obtain the fixed version (9.1.3.40197 or later) from the official Aruba Networks support portal
  3. 3. Follow Aruba's documented upgrade procedure for EdgeConnect Enterprise Orchestrator to apply the update
  4. 4. After upgrade completion, verify the system is functioning correctly
  5. 5. Confirm the running version is 9.1.3.40197 or later by checking the Orchestrator management interface

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

Fix this in Aruba Edgeconnect Enterprise Orchestrator Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-37915 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