Aruba Edgeconnect Enterprise OrchestratorWeb browser · Arubanetworks

CVE-2022-43523

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. An authenticated attacker can inject malicious SQL queries through unsanitized input fields in the management interface, allowing access to, modification of, or extraction of sensitive data from the underlying database. In severe cases, this can lead to full compromise of the Orchestrator host.

MitigationApply the vendor-supplied patches for affected versions (9.2.1.40179 and below, 9.1.4.40436 and below, 9.0.7.40110 and below, 8.10.23.40015 and below) or upgrade to a fixed release. Restrict access to the management interface to trusted users only until patching is complete.

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. Identify the installed EdgeConnect Enterprise Orchestrator version
    Access the web management interface and navigate to the 'About' or 'System Information' page, or check the version via CLI if available on the host
    Affected if The displayed version falls within any of these ranges: <= 8.10.23.40015, >= 9.0.0 and <= 9.0.7.40110, >= 9.1.0 and <= 9.1.4.40436, or >= 9.2.0 and <= 9.2.1.40179
  2. Confirm web-based management interface accessibility
    Determine if the management web interface is reachable on the network by attempting to access the host on common management ports (e.g., 443, 8443)
    Affected if The management interface is exposed and reachable from networks other than trusted administrative networks
  3. Verify authentication is required for the management interface
    Attempt to access the management interface without credentials or verify that a login challenge is presented
    Affected if The management interface can be accessed without being prompted for valid authentication credentials
  4. Review management interface logs for SQL injection indicators
    Examine the Orchestrator logs (typically found in /var/log/ or within the management UI logs section) for unusual SQL syntax, database errors, or suspicious query patterns in the time period of potential exploitation
    Affected if Logs contain database errors, malformed SQL statements, or evidence of SQL injection attempts
  5. Check for unauthorized database modifications or data exfiltration
    Review database tables or audit logs for unexpected changes, new administrative accounts, or unusual data access patterns that deviate from normal administrative activity
    Affected if Database contains unauthorized changes, unexpected privileged accounts, or evidence of unauthorized data access

The environment is affected if the installed EdgeConnect Enterprise Orchestrator version falls within the vulnerable ranges AND the management interface is accessible to an attacker.

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 affected versions (9.2.1.40179 and below, 9.1.4.40436 and below, 9.0.7.40110 and below, 8.10.23.40015 and below) or upgrade to a fixed release. Restrict access to the management interface to trusted users only until patching is complete.

Recommended fix Moderate confidence

Upgrade to the next available version in your current branch beyond the vulnerable patch level (e.g., 9.2.2.x or later for 9.2.x branch)

  1. 1. Identify the currently deployed Aruba EdgeConnect Enterprise Orchestrator version by checking the web interface or command line
  2. 2. Based on the installed major version branch, upgrade to the first version that is beyond the vulnerable patch level: For branch 8.10.x, upgrade to any version > 8.10.23.40015; For branch 9.0.x, upgrade to any version > 9.0.7.40110; For branch 9.1.x, upgrade to any version > 9.1.4.40436; For branch 9.2.x, upgrade to any version > 9.2.1.40179
  3. 3. Obtain the upgrade package from the Aruba support portal at https://asp.arubanetworks.com or through your Aruba sales representative
  4. 4. Follow the standard Aruba EdgeConnect Enterprise Orchestrator upgrade procedure documented in the Aruba installation guide
  5. 5. After upgrade, verify the new version is running and confirm the vulnerability is remediated
  6. 6. Test the web-based management interface functionality to ensure the upgrade did not introduce any regressions
Caveat Review Aruba release notes for your target version to check for any breaking changes or required migration steps

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

Fix this in Aruba Edgeconnect Enterprise Orchestrator Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing16.0 h
  • Review / QA8.0 h
36.0 hours of engineering $6,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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