dbcve.org
Aruba Edgeconnect Enterprise OrchestratorWeb browser · Arubanetworks

CVE-2022-43520

HIGH · 8.8 CVSS v3.1 Published 2023-01-05
Fix available
A fix is available. Upgrade to after 9.2.1.40179 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
Multiple vulnerabilities in the web-based management interface of Aruba EdgeConnect Enterprise Orchestrator could allow an authenticated remote attacker to conduct SQL injection attacks against the Aruba EdgeConnect Enterprise Orchestrator instance. An attacker could exploit these vulnerabilities to obtain and modify sensitive information in the underlying database potentially leading to complete compromise of the Aruba EdgeConnect Enterprise Orchestrator host in Aruba EdgeConnect Enterprise Orchestration Software version(s): Aruba EdgeConnect Enterprise Orchestrator (on-premises), Aruba EdgeConnect Enterprise Orchestrator-as-a-Service, Aruba EdgeConnect Enterprise Orchestrator-SP and Aruba EdgeConnect Enterprise Orchestrator Global Enterprise Tenant Orchestrators - Orchestrator 9.2.1.40179 and below, - Orchestrator 9.1.4.40436 and below, - Orchestrator 9.0.7.40110 and below, - Orchestrator 8.10.23.40015 and below, - Any older branches of Orchestrator not specifically mentioned.

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

Multiple SQL injection vulnerabilities exist in the web-based management interface of Aruba EdgeConnect Enterprise Orchestrator. Authenticated remote attackers can exploit these vulnerabilities to inject malicious SQL queries, potentially allowing them to extract or modify sensitive data from the underlying database and achieve complete host compromise.

MitigationApply the vendor-supplied patches for all affected Orchestrator versions (9.2.2+, 9.1.5+, 9.0.8+, 8.10.24+) and restrict access to the management interface to trusted personnel only.

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:<= 8.10.23.40015>= 9.0.0, <= 9.0.7.40110>= 9.1.0, <= 9.1.4.40436>= 9.2.0, <= 9.2.1.40179

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. Confirm Aruba EdgeConnect Enterprise Orchestrator is installed
    Check if the web-based management interface is accessible by attempting to reach the Orchestrator login page (typically at HTTPS port 443 or a configured port). Look for the Orchestrator service running on the host.
    Affected if The Orchestrator web interface is reachable and responds with Aruba EdgeConnect login page.
  2. Identify the installed version
    Log into the web management interface and navigate to the About or System Information page, typically found under Help or System settings. Alternatively, access the Orchestrator CLI and run the command to display the software version.
    Affected if You can retrieve a specific version number from the web UI or CLI.
  3. Compare version against affected ranges
    Check if your installed version falls within any of these affected ranges: 8.10.x versions <= 8.10.23.40015; 9.0.x versions <= 9.0.7.40110; 9.1.x versions <= 9.1.4.40436; 9.2.x versions <= 9.2.1.40179
    Affected if Your installed version matches one of the affected ranges listed above.
  4. Verify web management interface is enabled
    Confirm the web-based management interface is actively running and accessible. Check if the service (typically named 'orchestrator' or similar) is in a running state and listening on its configured HTTP/HTTPS port.
    Affected if The web management interface service is running and accessible.

You are affected if the Aruba EdgeConnect Enterprise Orchestrator web interface is accessible and the installed version falls within any of the affected version ranges.

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

Apply the vendor-supplied patches for all affected Orchestrator versions (9.2.2+, 9.1.5+, 9.0.8+, 8.10.24+) and restrict access to the management interface to trusted personnel only.

Recommended fix Moderate confidence

Latest stable version of Aruba EdgeConnect Enterprise Orchestrator beyond 9.2.1.40179 (e.g., 9.2.2 or later stable branch)

  1. 1. Identify the currently deployed Aruba EdgeConnect Enterprise Orchestrator version through the web management interface or command line
  2. 2. If running version 8.10.x, upgrade to version 8.10.23.40016 or later
  3. 3. If running version 9.0.x, upgrade to version 9.0.7.40111 or later
  4. 4. If running version 9.1.x, upgrade to version 9.1.4.40437 or later
  5. 5. If running version 9.2.x, upgrade to version 9.2.2 or later (version that exceeds 9.2.1.40179)
  6. 6. After upgrade, verify the new version is running and confirm the SQL injection vulnerability is remediated
  7. 7. Test critical business workflows to ensure the upgrade did not introduce functionality issues
Caveat Review Aruba release notes for the target version for any configuration or behavioral changes; test in non-production environment before deploying to production

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

Fix this in Aruba Edgeconnect Enterprise Orchestrator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
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,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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