dbcve.org
Edgeconnect Sd Wan OrchestratorWeb browser · Arubanetworks

CVE-2024-22443

HIGH · 8.8 CVSS v3.1 Published 2024-07-24
Fix available
A fix is available. Upgrade to 9.1.10 / 9.2.10 or later.
See remediation →
94/100
Remediation priority · Urgent
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 conduct a server-side prototype pollution attack. Successful exploitation of this vulnerability could allow an attacker to execute arbitrary commands 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

A server-side prototype pollution vulnerability exists in the web-based management interface of EdgeConnect SD-WAN Orchestrator. An authenticated attacker can exploit this flaw to inject or modify object prototypes, ultimately achieving arbitrary command execution on the underlying operating system with full system compromise as the result.

MitigationApply the vendor-provided patch for CVE-2024-22443 and restrict access to the management interface to trusted internal IP addresses only. Additionally, review user accounts with access to the Orchestrator for necessity and rotate credentials as a precautionary measure.

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.1.0, < 9.1.10>= 9.2.0, < 9.2.10>= 9.3.0, < 9.3.3>= 9.4.0, < 9.4.2

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
High

CVSS:3.1/AV:N/AC:L/PR:L/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 EdgeConnect SD-WAN Orchestrator version
    Access the web management interface and navigate to the About or System Information page, or use the CLI command 'show version' if available via SSH or console
    Affected if The displayed version falls within any of these ranges: 9.1.0 to 9.1.9, 9.2.0 to 9.2.9, 9.3.0 to 9.3.2, or 9.4.0 to 9.4.1
  2. Verify web management interface accessibility
    Confirm the web-based management interface is reachable by accessing the Orchestrator URL over HTTPS on ports 443 or 8443, or whichever port is configured
    Affected if The web management interface is exposed and accessible from a network where untrusted users could potentially connect
  3. Confirm authentication status
    Verify whether valid user accounts exist in the Orchestrator system and check if authentication is required to access the management interface
    Affected if Active user accounts with valid credentials exist for the management interface, as the vulnerability requires an authenticated attacker to exploit the prototype pollution flaw

You are affected if the installed Orchestrator version is within the affected ranges AND the web management interface is accessible with valid authentication 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.

dbcve · scoped
Upgrade available Upgrade to 9.1.10 / 9.2.10 / 9.3.3 or later
Fixed in 9.1.109.2.109.3.3
Interim mitigation

Apply the vendor-provided patch for CVE-2024-22443 and restrict access to the management interface to trusted internal IP addresses only. Additionally, review user accounts with access to the Orchestrator for necessity and rotate credentials as a precautionary measure.

Recommended fix High confidence

Upgrade to 9.1.10 (for 9.1.x), 9.2.10 (for 9.2.x), 9.3.3 (for 9.3.x), or 9.4.2 (for 9.4.x)

  1. Identify the currently installed EdgeConnect SD-WAN Orchestrator version using the web interface or CLI
  2. If running 9.1.x, upgrade to version 9.1.10 or later
  3. If running 9.2.x, upgrade to version 9.2.10 or later
  4. If running 9.3.x, upgrade to version 9.3.3 or later
  5. If running 9.4.x, upgrade to version 9.4.2 or later
  6. Obtain the upgrade package from the HPE support portal (support.hpe.com)
  7. Schedule a maintenance window and follow HPE's standard upgrade procedure for EdgeConnect Orchestrator
  8. After upgrade, verify the management interface is accessible and confirm the new version number
Caveat Review HPE release notes for any configuration or feature changes between versions; standard minor version upgrades typically have minimal disruption

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

Fix this in Edgeconnect Sd Wan Orchestrator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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