CVE-2023-37428
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 · uneditedA vulnerability in the EdgeConnect SD-WAN Orchestrator web-based management interface allows 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.
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 EdgeConnect SD-WAN Orchestrator web-based management interface allows remote authenticated attackers to execute arbitrary commands as root on the underlying host operating system, resulting in complete system compromise.
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>= 9.0.0, <= 9.0.5>= 9.1.0, <= 9.1.7>= 9.2.0, <= 9.2.5= 9.3.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 EdgeConnect SD-WAN Orchestrator installationLocate the Orchestrator installation directory or check system services for processes related to EdgeConnect. Common paths include /opt/edgeconnect or check for the 'orchestrator' service process.Affected if The product is installed on the system
-
Determine installed Orchestrator versionCheck the version of the installed EdgeConnect SD-WAN Orchestrator. This is typically available via the web management interface login page, in the product UI under 'About' or 'System Information', or via CLI command such as 'show version' if SSH access is available.Affected if The installed version falls within 9.0.0-9.0.5, 9.1.0-9.1.7, 9.2.0-9.2.5, or 9.3.0
-
Verify web management interface is enabledCheck if the web-based management interface is enabled and accessible. This can be done by attempting to access the management URL (typically on port 443 or 8443) or by checking the Orchestrator configuration files for web interface settings.Affected if The web management interface is enabled and reachable
-
Confirm authentication is required for management interfaceVerify that the web management interface requires authentication. Check if unauthenticated access is possible or if default/weak credentials are in use. Review authentication configuration in the Orchestrator settings.Affected if The management interface allows authenticated access, making exploitation possible
The environment is affected if EdgeConnect SD-WAN Orchestrator is installed with a version in the affected ranges (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 enabled and accessible with valid credentials.
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-provided security patches when available; restrict access to the management interface to trusted networks/IPs and enforce strong authentication to reduce attack surface.
Upgrade to EdgeConnect SD-WAN Orchestrator version 9.3.1 or later (for branch 9.3.x), or upgrade to the latest available version in your supported branch (9.0.x should go to 9.0.6+, 9.1.x to 9.1.8+, 9.2.x to 9.2.6+)
- 1. Back up the current EdgeConnect SD-WAN Orchestrator configuration.
- 2. Schedule a maintenance window for the upgrade.
- 3. Download the latest EdgeConnect SD-WAN Orchestrator version (9.3.1 or later) from the Aruba support portal.
- 4. Follow Aruba's standard upgrade procedure documented in the EdgeConnect installation guide.
- 5. After upgrade, verify the Orchestrator web interface is accessible and functioning normally.
- 6. Confirm the version upgrade was successful by checking the web-based management interface version number.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,760.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37428 — 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-2023-37428 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