# CVE-2022-44565: Information disclosure in UISP Wireless

> An attacker can retrieve status and usage data from UISP devices due to improper access validation, requiring a firmware upgrade.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 23 Dec 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-c9cm-rvww-38hx

## What is CVE-2022-44565?

CVE-2022-44565 is a medium-severity vulnerability in UISP Wireless, published on 23 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An improper access validation vulnerability exists in airMAX AC <8.7.11, airFiber 60/LR <2.6.2, airFiber 60 XG/HD <v1.0.0 and airFiber GBE <1.4.1 that allows a malicious actor to retrieve status and usage data from the UISP device.

Weakness: CWE-284 (Improper Access Control)

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

It affects 6 products.


Products: Ui Airfiber 60-Hd Firmware, Ui Airfiber 60-Lr Firmware, Ui Airfiber 60-Xg Firmware, Ui Airfiber 60 Firmware, Ui Airfiber Gigabeam Firmware, Ui Airmax Ac Firmware.

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

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

## Is CVE-2022-44565 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-44565 is a medium-severity vulnerability in UISP Wireless, published on 23 Dec 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-44565 in the wild and no public exploit code.

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

## Sources

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

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