dbcve.org
Edgeconnect Sd Wan OrchestratorWeb browser · Arubanetworks

CVE-2023-37431

HIGH · 8.1 CVSS v3.1 Published 2023-08-22
Fix available
A fix is available. Upgrade to after 9.2.5 or later.
See remediation →
87/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
Multiple vulnerabilities in the web-based management interface of EdgeConnect SD-WAN Orchestrator could allow an authenticated remote attacker to conduct SQL injection attacks against the EdgeConnect SD-WAN Orchestrator instance. An attacker could exploit these vulnerabilities to     obtain and modify sensitive information in the underlying database potentially leading to the exposure and corruption of sensitive data controlled by the EdgeConnect SD-WAN Orchestrator host.

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 · moderate confidence

Multiple SQL injection vulnerabilities exist in the web-based management interface of EdgeConnect SD-WAN Orchestrator. An authenticated remote attacker can inject malicious SQL queries through the interface to access, exfiltrate, or corrupt sensitive data in the underlying database.

MitigationApply vendor-supplied patches when released. Until then, restrict management interface access to trusted IPs only, enforce least-privilege database accounts, and consider deploying a WAF to filter SQL injection attempts.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

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. Confirm EdgeConnect SD-WAN Orchestrator is deployed
    Identify if Aruba Networks EdgeConnect SD-WAN Orchestrator software is installed in your environment. Check installed applications, system inventory, or documentation for this product.
    Affected if The product is not present in your environment, this CVE does not apply.
  2. Determine the installed version
    Locate the version number of your EdgeConnect SD-WAN Orchestrator installation. This is typically found in the web management interface (often in About or System Info pages), in the system console, or in installation/upgrade documentation.
    Affected if Unable to determine the version means you cannot assess if you are in the affected range.
  3. Compare version to affected ranges
    Match your installed version against the following affected ranges: 9.0.0 through 9.0.5, 9.1.0 through 9.1.7, 9.2.0 through 9.2.5, or exactly version 9.3.0
    Affected if Your installed version falls within any of these ranges: 9.0.x where x is 0-5, 9.1.x where x is 0-7, 9.2.x where x is 0-5, or exactly 9.3.0.
  4. Verify web management interface accessibility
    Determine if the EdgeConnect SD-WAN Orchestrator web-based management interface is accessible from network locations where untrusted users could connect. Check firewall rules, VPN requirements, and interface binding configurations.
    Affected if The web interface is exposed to untrusted network segments, the vulnerability could be exploited by an authenticated attacker.
  5. Confirm authentication is required for the interface
    Verify that the web management interface requires valid authentication credentials to access. Check authentication settings, user account configurations, and whether anonymous access is permitted.
    Affected if The interface permits unauthenticated access, the specific SQL injection path may differ but the exposure is greater.

You are affected if EdgeConnect SD-WAN Orchestrator is installed and your version falls within 9.0.0-9.0.5, 9.1.0-9.1.7, 9.2.0-9.2.5, or is exactly 9.3.0, and the web management interface is accessible to potential attackers.

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.5
Interim mitigation

Apply vendor-supplied patches when released. Until then, restrict management interface access to trusted IPs only, enforce least-privilege database accounts, and consider deploying a WAF to filter SQL injection attempts.

Recommended fix Moderate confidence

Upgrade to 9.0.6+ (for 9.0.x), 9.1.8+ (for 9.1.x), 9.2.6+ (for 9.2.x), or 9.3.1+ (for 9.3.x) - or migrate to the latest stable 9.x release

  1. 1. Identify the currently installed EdgeConnect SD-WAN Orchestrator version in your environment.
  2. 2. Determine which version branch you are running (9.0.x, 9.1.x, 9.2.x, or 9.3.x).
  3. 3. Download the corresponding patched version from Aruba's support portal or software distribution channel: For 9.0.x branch, upgrade to 9.0.6 or later; For 9.1.x branch, upgrade to 9.1.8 or later; For 9.2.x branch, upgrade to 9.2.6 or later; For 9.3.x branch, upgrade to 9.3.1 or later.
  4. 4. Review Aruba's release notes for the target version to confirm the security fix is included.
  5. 5. Create a backup of the current Orchestrator configuration before upgrading.
  6. 6. Schedule a maintenance window as the upgrade will require Orchestrator downtime.
  7. 7. Execute the upgrade following Aruba's standard upgrade procedures for EdgeConnect SD-WAN Orchestrator.
  8. 8. After upgrade, verify the Orchestrator is operational and the web interface is accessible.
Caveat Minor version upgrades typically have low risk but always review release notes for any configuration or compatibility changes before applying in production

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

Fix this in Edgeconnect Sd Wan Orchestrator Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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