CVE-2022-43524
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 · uneditedA vulnerability in the web-based management interface of Aruba EdgeConnect Enterprise Orchestrator could allow an authenticated remote attacker to conduct a stored cross-site scripting (XSS) attack against an administrative user of the interface. A successful exploit allows 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 confidenceA stored cross-site scripting (XSS) vulnerability exists in the web-based management interface of Aruba EdgeConnect Enterprise Orchestrator. An authenticated attacker can inject malicious script code into the interface that executes when an administrative user views the compromised content, allowing the attacker to steal session cookies or perform actions as the victim user.
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<= 8.10.23.40015>= 9.0.0, <= 9.0.7.40110>= 9.1.0, <= 9.1.4.40436>= 9.2.0, <= 9.2.1.40179CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Orchestrator versionAccess the web management interface and navigate to the About or System Information page to view the exact version number, or use the CLI command 'show version' if availableAffected 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
-
Confirm web management interface is enabledVerify that the web-based management interface (HTTPS admin portal) is accessible and active by attempting to reach the login pageAffected if The web interface is exposed and accessible to authenticated users, which is required for the XSS to be exploitable
-
Review system logs for suspicious script injection patternsExamine Orchestrator logs (typically found in /var/log/ or via the logging section in the web UI) for entries containing HTML script tags, javascript:, or encoded XSS payloads in user-supplied fields such as device names, descriptions, or configuration fieldsAffected if Log entries show evidence of script injection attempts or unexpected HTML/script content in fields that should only contain plain text
-
Audit administrative user sessions and recent actionsReview active administrative sessions and audit logs to identify any actions performed by users that were not initiated by legitimate administrators, particularly changes to system configuration, user accounts, or policiesAffected if There are unexplained administrative actions or sessions that do not correspond to known administrator activity
A user is affected if the installed Orchestrator version is within the affected ranges listed and the web management interface is accessible, allowing an authenticated attacker to inject persistent malicious scripts.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the vendor-provided patch or upgrade to a fixed version (Orchestrator 9.2.1.40180 and above, 9.1.4.40437 and above, 9.0.7.40111 and above, or 8.10.23.40016 and above). Until patching is feasible, implement Content Security Policy (CSP) headers and disable JavaScript in administrative sessions where possible.
Aruba EdgeConnect Enterprise Orchestrator 8.10.23.40016+, 9.0.7.40111+, 9.1.4.40437+, 9.2.1.40180+, or latest 9.x branch
- Identify your current Aruba EdgeConnect Enterprise Orchestrator version in the web-based management interface under 'Help > About' or via the CLI
- For Orchestrator 8.10.x branch: Upgrade to version 8.10.23.40016 or later
- For Orchestrator 9.0.x branch: Upgrade to version 9.0.7.40111 or later
- For Orchestrator 9.1.x branch: Upgrade to version 9.1.4.40437 or later
- For Orchestrator 9.2.x branch: Upgrade to version 9.2.1.40180 or later
- Alternatively, migrate to the latest stable 9.x release (9.2.2 or higher if available) to receive all security patches
- After upgrade, verify the XSS vulnerability is remediated by confirming the fixed version is running
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43524 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-43524 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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