Edgeconnect Sd Wan OrchestratorWeb browser · Arubanetworks

CVE-2023-37427

HIGH · 7.2 CVSS v3.1 Published 2023-08-22
Fix available
A fix is available. Upgrade to after 9.2.5 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
A vulnerability in the web-based management interface of EdgeConnect SD-WAN Orchestrator could allow an authenticated remote attacker to run arbitrary commands on the underlying host. Successful exploitation of this vulnerability allows an attacker to execute arbitrary commands as root on the underlying operating system leading to complete system compromise.

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

Authenticated command injection vulnerability in EdgeConnect SD-WAN Orchestrator web-based management interface allows remote attackers to execute arbitrary commands as root on the underlying operating system, leading to complete system compromise.

MitigationApply vendor-supplied patch for EdgeConnect SD-WAN Orchestrator; restrict management interface access to trusted networks/IPs until patch is applied.

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 Sd Wan OrchestratorWeb browser
Affected:>= 9.0.0, <= 9.0.5>= 9.1.0, <= 9.1.7>= 9.2.0, <= 9.2.5= 9.3.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 installed product
    Locate the EdgeConnect SD-WAN Orchestrator instance in your environment. This is typically a virtual appliance or hardware appliance providing SD-WAN orchestration services.
    Affected if The target system is not Aruba Networks EdgeConnect SD-WAN Orchestrator.
  2. Determine the installed version
    Access the web-based management interface and navigate to the system information or about page to find the software version. Alternatively, check the appliance console or API for version details.
    Affected if The installed version falls within these ranges: 9.0.0-9.0.5, 9.1.0-9.1.7, 9.2.0-9.2.5, or 9.3.0 exactly.
  3. Verify web management interface accessibility
    Confirm whether the web-based management interface is exposed to the network. Attempt to access the management URL from a non-local network segment or conduct a port scan for HTTP/HTTPS services on the orchestrator.
    Affected if The web management interface is accessible from untrusted networks.
  4. Check authentication configuration
    Review user accounts and authentication settings for the management interface. Determine if default or weak credentials are in use, or if the authentication mechanism can be bypassed.
    Affected if An attacker can obtain valid authentication credentials to access the management interface.

Your environment is affected if you are running EdgeConnect SD-WAN Orchestrator versions 9.0.0-9.0.5, 9.1.0-9.1.7, 9.2.0-9.2.5, or 9.3.0, and the web management interface is accessible to an attacker who can obtain valid credentials.

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.

From vendor data
Upgrade available Upgrade to a release after 9.2.5
Interim mitigation

Apply vendor-supplied patch for EdgeConnect SD-WAN Orchestrator; restrict management interface access to trusted networks/IPs until patch is applied.

Fix this in Edgeconnect Sd Wan Orchestrator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,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 $4,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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