dbcve.org
Aruba Edgeconnect Enterprise OrchestratorWeb browser · Arubanetworks

CVE-2022-43528

MEDIUM · 6.5 CVSS v3.1 Published 2023-01-05
Fix available
A fix is available. Upgrade to after 9.2.1.40179 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Under certain configurations, an attacker can login to Aruba EdgeConnect Enterprise Orchestrator without supplying a multi-factor authentication code. Successful exploitation allows an attacker to login using only a username and password and successfully bypass MFA requirements 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

This is an authentication bypass vulnerability in Aruba EdgeConnect Enterprise Orchestrator where, under certain configurations, an attacker can login using only username and password without providing the required multi-factor authentication code, effectively bypassing MFA protections.

MitigationUpgrade Aruba EdgeConnect Enterprise Orchestrator to a version newer than the specified vulnerable versions (9.2.1.40179, 9.1.4.40436, 9.0.7.40110, 8.10.23.40015) and review MFA configuration settings to ensure they are properly enforced.

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Aruba EdgeConnect Enterprise Orchestrator version
    Access the Orchestrator admin UI and navigate to System > About, or use the command line interface to query the installed software version
    Affected if The installed version falls within any of these vulnerable ranges: 8.10.x up to 8.10.23.40015; 9.0.x up to 9.0.7.40110; 9.1.x up to 9.1.4.40436; 9.2.0 through 9.2.1.40179
  2. Confirm MFA is configured on the system
    Navigate to Identity Management > Authentication Methods or System > Security settings in the Orchestrator UI to verify if Multi-Factor Authentication is enabled for user logins
    Affected if MFA is enabled or required for authentication on this instance
  3. Verify authentication bypass vulnerability exists
    Attempt a login using valid username and password credentials without providing the MFA code, or review authentication logs for successful logins that bypassed the second factor
    Affected if Login succeeds without providing the MFA token when MFA is configured, indicating the bypass is present
  4. Review MFA enforcement settings
    Check System > Security > Multi-Factor Authentication settings to confirm MFA policy is set to Required or Mandatory rather than Optional
    Affected if MFA is configured as required but can be circumvented through the vulnerability

A user is affected if their Aruba EdgeConnect Enterprise Orchestrator version is within the vulnerable ranges AND MFA is enabled, allowing authentication to succeed with only username and password without the second factor.

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

Upgrade Aruba EdgeConnect Enterprise Orchestrator to a version newer than the specified vulnerable versions (9.2.1.40179, 9.1.4.40436, 9.0.7.40110, 8.10.23.40015) and review MFA configuration settings to ensure they are properly enforced.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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