# 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

> Unauthenticated remote attackers can bypass authentication to gain administrative privileges and completely compromise the Aruba EdgeConnect Enterprise Orchestrator.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Oct 2022
- **Updated:** 7 May 2025
- **Also known as:** GHSA-548r-qhxq-rvvv

## What is CVE-2022-37913?

CVE-2022-37913 is a critical authentication bypass vulnerability 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, published on 28 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerabilities in the web-based management interface of Aruba EdgeConnect Enterprise Orchestrator could allow an unauthenticated remote attacker to bypass authentication. Successful exploitation of these vulnerabilities could allow an attacker to gain administrative privileges leading to a complete compromise of the Aruba EdgeConnect Enterprise Orchestrator with versions 9.1.2.40051 and below, 9.0.7.40108 and below, 8.10.23.40009 and below, and any older branches of Orchestrator not specifically mentioned.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Arubanetworks Aruba Edgeconnect Enterprise Orchestrator.

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

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

## Is CVE-2022-37913 being exploited?

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

## Other vulnerabilities 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

- [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)
- [CVE-2022-43521](https://insights.sbomify.com/CVE-2022-43521/): SQL injection in Aruba EdgeConnect Enterprise Orchestration Software (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-37913 is a critical authentication bypass vulnerability 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, published on 28 Oct 2022. 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-37913 in the wild and no public exploit code.

Affected product: 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. 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-37913/ (Markdown: https://insights.sbomify.com/CVE-2022-37913/index.md)
```

## Sources

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

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