# CVE-2022-3010: Predictable SSH credentials in Priva TopControl Suite

> Attackers can calculate SSH credentials based on serial numbers to gain unauthorized access to Priva TopControl Suite devices.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 2 Jan 2024
- **Updated:** 4 Jun 2025
- **Also known as:** GHSA-x5gw-mqgf-fwh3

## What is CVE-2022-3010?

CVE-2022-3010 is a high-severity vulnerability in Priva TopControl Suite - Bacnet, published on 2 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Priva TopControl Suite contains predictable credentials for the SSH service, based on the Serial number. Which makes it possible for an attacker to calculate the login credentials for the Priva TopControll suite.

Weakness: CWE-916 (Use of Password Hash With Insufficient Computational Effort), CWE-1391 (Use of Weak Credentials)

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

It affects 1 product.


Products: Priva Top Control Suite.

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

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

## Is CVE-2022-3010 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3010 is a high-severity vulnerability in Priva TopControl Suite - Bacnet, published on 2 Jan 2024. 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-3010 in the wild and no public exploit code.

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

## Sources

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

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