dbcve.org
Aruba Edgeconnect Enterprise OrchestratorWeb browser · Arubanetworks

CVE-2022-43525

MEDIUM · 6.1 CVSS v3.1 Published 2023-01-05
Fix available
A fix is available. Upgrade to after 9.2.1.40179 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 within the web-based management interface of Aruba EdgeConnect Enterprise Orchestrator could allow a remote attacker to conduct a reflected cross-site scripting (XSS) attack against a user of the interface. A successful exploit could allow an attacker to execute arbitrary script code in a victim's browser in the context of the affected interface 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

Reflected XSS vulnerabilities in the web-based management interface of Aruba EdgeConnect Enterprise Orchestrator allow remote attackers to execute arbitrary JavaScript in victim's browsers by tricking users into clicking malicious links containing crafted payloads.

MitigationApply vendor-provided patches for affected Orchestrator versions (9.2.1.40180+, 9.1.4.40437+, 9.0.7.40111+, 8.10.23.40016+) and implement input validation/output encoding as defense-in-depth.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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. Verify web management interface is accessible
    Attempt to access the Aruba EdgeConnect Enterprise Orchestrator web interface via HTTPS on ports 443 or 8443 (or the configured port). If the login page or management console loads, the web interface is exposed.
    Affected if The web interface is exposed to network (internal or external) - this is required for the reflected XSS to be exploitable
  2. Locate the installed Orchestrator version
    Check the version displayed on the web login page, in the About section of the management interface, or via CLI command 'show version' or 'show system info' if you have CLI access.
    Affected if You are unable to determine the version - but if you can access the interface, proceed to version comparison
  3. Compare your version against affected ranges
    Match your installed version to the following affected ranges: 8.10.x <= 8.10.23.40015; 9.0.x <= 9.0.7.40110; 9.1.x <= 9.1.4.40436; 9.2.x <= 9.2.1.40179. Versions prior to 8.10, or any version NEWER than 9.2.1.40179 for the 9.2 branch (and similarly newer for other branches), are not listed as affected.
    Affected if Your installed version falls within ANY of these ranges: <= 8.10.23.40015, 9.0.0-9.0.7.40110, 9.1.0-9.1.4.40436, or 9.2.0-9.2.1.40179

You are affected if the web-based management interface is accessible AND your installed Orchestrator version matches any of the four 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 vendor-provided patches for affected Orchestrator versions (9.2.1.40180+, 9.1.4.40437+, 9.0.7.40111+, 8.10.23.40016+) and implement input validation/output encoding as defense-in-depth.

Recommended fix High confidence

Upgrade to the latest available version in your current branch: 8.10.24+, 9.0.8+, 9.1.5+, or 9.2.2+ (or the latest overall release)

  1. 1. Identify the currently installed Aruba EdgeConnect Enterprise Orchestrator version via the web management interface or CLI
  2. 2. Determine which version branch your installation falls into (8.x, 9.0.x, 9.1.x, or 9.2.x)
  3. 3. For version 8.10.x: Upgrade to version 8.10.24.0 or later
  4. 4. For version 9.0.x: Upgrade to version 9.0.8.0 or later
  5. 5. For version 9.1.x: Upgrade to version 9.1.5.0 or later
  6. 6. For version 9.2.x: Upgrade to version 9.2.2.0 or later
  7. 7. After upgrade, verify the new version in the web management interface under the 'About' or 'System Information' section
  8. 8. Test that the web interface functions normally after the upgrade
Caveat Review Aruba's release notes for your target version for any configuration or behavioral changes before upgrading

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

Fix this in Aruba Edgeconnect Enterprise Orchestrator Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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