# CVE-2022-43528: Auth bypass in Aruba EdgeConnect Enterprise Orchestration Software

> Attackers can bypass multi-factor authentication to log in with only credentials, requiring specific configurations in Aruba EdgeConnect Orchestrator.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jan 2023
- **Updated:** 10 Apr 2025
- **Also known as:** GHSA-2f52-v87j-7ppj

## What is CVE-2022-43528?

CVE-2022-43528 is a medium-severity authentication bypass vulnerability in Hewlett Packard Enterprise (HPE) Aruba EdgeConnect Enterprise Orchestration Software, published on 3 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2022-43528?

It affects 1 product.


Products: Arubanetworks Aruba Edgeconnect Enterprise Orchestrator.

## How do I fix CVE-2022-43528?

No fix has been published for CVE-2022-43528 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-43528 being exploited?

There is no known exploitation of CVE-2022-43528 in the wild and no public exploit code.

## Other vulnerabilities in Hewlett Packard Enterprise (HPE) Aruba EdgeConnect Enterprise Orchestration Software

- [CVE-2022-37913](https://insights.sbomify.com/CVE-2022-37913/): Auth bypass in 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 (critical 9.8)
- [CVE-2022-37914](https://insights.sbomify.com/CVE-2022-37914/): Auth bypass in 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 (critical 9.8)
- [CVE-2022-37915](https://insights.sbomify.com/CVE-2022-37915/): Command injection in Aruba EdgeConnect Enterprise Orchestrator (on-premises) (critical 9.8)
- [CVE-2022-43519](https://insights.sbomify.com/CVE-2022-43519/): SQL injection in Aruba EdgeConnect Enterprise Orchestration Software (high 8.8)
- [CVE-2022-43520](https://insights.sbomify.com/CVE-2022-43520/): SQL injection in Aruba EdgeConnect Enterprise Orchestration Software (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-43528 and fix it if it is affected.

What it is: CVE-2022-43528 is a medium-severity authentication bypass vulnerability in Hewlett Packard Enterprise (HPE) Aruba EdgeConnect Enterprise Orchestration Software, published on 3 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-43528 in the wild and no public exploit code.

Affected product: Hewlett Packard Enterprise (HPE) Aruba EdgeConnect Enterprise Orchestration Software. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-43528/ (Markdown: https://insights.sbomify.com/CVE-2022-43528/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-43528
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-43528
- OSV: https://osv.dev/vulnerability/CVE-2022-43528

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-43528/
Summaries are generated and may contain mistakes; the official description above is the record.