CVE-2022-43529
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 remote attacker to persist a session after a password reset or similar session clearing event. Successful exploitation of this vulnerability could allow an authenticated attacker to remain on the system with the permissions of their current session after the session should be invalidated 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 confidenceThis is a session management vulnerability in Aruba EdgeConnect Enterprise Orchestrator's web-based management interface. The interface fails to properly invalidate existing user sessions when a password reset occurs or during similar session-clearing events. An authenticated attacker can exploit this to retain their session privileges and remain on the system even after their session should have been terminated.
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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 the installed EdgeConnect Enterprise Orchestrator versionLog into the web-based management interface and locate the version information typically displayed on the login page, in the About section, or in the system settings. Alternatively, access the appliance via CLI and use commands such as 'show version' or 'show system info' to retrieve the installed software version.Affected if The displayed version falls within any of these ranges: <= 8.10.23.40015, >= 9.0.0 through 9.0.7.40110, >= 9.1.0 through 9.1.4.40436, or >= 9.2.0 through 9.2.1.40179
-
Confirm the web-based management interface is enabledVerify that the web-based management interface is active on the appliance. This can be done by checking the management service configuration via CLI commands such as 'show web-server status' or reviewing the management access settings in the web UI under System > Administration > Management Access.Affected if The web-based management interface is enabled and accessible, which is required for this vulnerability to be exploitable
-
Verify session invalidation behavior after password resetAs an authenticated user with access to the web management interface, initiate a password change for your own account or another account. After the password is changed, attempt to use a previously active session (such as an existing browser session or API token) to access the system. Observe whether the old session remains valid and retains its privileges.Affected if The old session remains active and fully functional after a password reset, indicating that sessions are not being properly invalidated - this confirms the vulnerability is present
Your environment is affected if the installed EdgeConnect Enterprise Orchestrator version falls within any of the affected version ranges AND the web-based management interface is enabled, particularly if old sessions remain valid after password reset or similar session-clearing events.
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.
From vendor dataApply the vendor-supplied patches or upgrade to fixed versions of Aruba EdgeConnect Enterprise Orchestrator: 9.2.1.40180 or higher for branch 9.2.x, 9.1.4.40437 or higher for branch 9.1.x, 9.0.7.40111 or higher for branch 9.0.x, and 8.10.23.40016 or higher for branch 8.10.x.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43529 — 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-43529 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