# CVE-2022-39185: EXFO - BV-10 Performance Endpoint Unit Undocumented privileged user.

> An attacker can gain privileged access to the EXFO BV-10 unit using an undocumented hard-coded user account.

- **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:** 12 Jan 2023
- **Updated:** 8 Apr 2025
- **Also known as:** GHSA-qhfg-3j7q-77q7

## What is CVE-2022-39185?

CVE-2022-39185 is a critical vulnerability in EXFO BV-10 Performance Endpoint Unit, published on 12 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

EXFO - BV-10 Performance Endpoint Unit Undocumented privileged user. Unit has an undocumented hard-coded privileged user.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Exfo Bv-10 Firmware.

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

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

## Is CVE-2022-39185 being exploited?

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

## Other vulnerabilities in EXFO BV-10 Performance Endpoint Unit

- [CVE-2022-39184](https://insights.sbomify.com/CVE-2022-39184/): EXFO - BV-10 Performance Endpoint Unit Authentication bypass (critical 9.8)
- [CVE-2022-39186](https://insights.sbomify.com/CVE-2022-39186/): EXFO - BV-10 Performance Endpoint Unit Misconfiguration (medium 6.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-39185 is a critical vulnerability in EXFO BV-10 Performance Endpoint Unit, published on 12 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-39185 in the wild and no public exploit code.

Affected product: EXFO BV-10 Performance Endpoint Unit. 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-39185/ (Markdown: https://insights.sbomify.com/CVE-2022-39185/index.md)
```

## Sources

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

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