dbcve.org
Aruba Edgeconnect Enterprise OrchestratorWeb browser · Arubanetworks

CVE-2022-43521

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 in the web-based management interface of Aruba EdgeConnect Enterprise Orchestrator allow authenticated remote attackers to inject arbitrary SQL queries, potentially exposing or modifying sensitive database information and achieving complete host compromise.

MitigationApply Aruba's security patches or upgrade to versions beyond 9.2.1.40179, 9.1.4.40436, 9.0.7.40110, and 8.10.23.40015 as specified in the Aruba security advisory.

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 Aruba EdgeConnect Enterprise Orchestrator deployment
    Locate systems running Aruba EdgeConnect Enterprise Orchestrator in your environment. Check inventory systems or network scans for this product.
    Affected if The product is Aruba EdgeConnect Enterprise Orchestrator
  2. Determine the installed version
    Log into the web-based management interface and look for the version information typically displayed in the UI footer, About page, or system status page. Alternatively, access the CLI and run commands such as 'show version' or 'show system information' to retrieve the software version.
    Affected if The installed 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; >= 9.2.0 and <= 9.2.1.40179
  3. Confirm web-based management interface is accessible
    Verify that the web management interface is reachable on the typical HTTPS ports (443 or 8443) for your Orchestrator instances. Check firewall rules and network access controls.
    Affected if The web management interface is exposed and reachable from a network where attackers could authenticate
  4. Check for existing user authentication
    Review authentication configuration to confirm that user accounts exist in the system. The SQL injection requires valid credentials to exploit.
    Affected if User accounts are configured in the Orchestrator, providing a potential attack vector for authenticated SQL injection

You are affected if Aruba EdgeConnect Enterprise Orchestrator is running a version within the affected ranges AND the web-based management interface is accessible with valid user 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.

From vendor data
Upgrade available Upgrade to a release after 9.2.1.40179
Interim mitigation

Apply Aruba's security patches or upgrade to versions beyond 9.2.1.40179, 9.1.4.40436, 9.0.7.40110, and 8.10.23.40015 as specified in the Aruba security advisory.

Fix this in Aruba Edgeconnect Enterprise Orchestrator Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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