Skip to content
Fencer Vulns
high 7.5

CVE-2022-3010 json

Predictable SSH credentials in Priva TopControl Suite

published 2024-01-02 2 y ago modified 2026-06-17 4 mo ago also EUVD-2022-42446

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 48%
public exploits
0
none known

Summary

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.

Patch / fix

  • Priva TopControl Suite - Bacnet 8.7.8.0
  • Priva TopControl Suite - Blue ID 8.7.8.0
  • Priva TopControl Suite - Compass 8.7.8.0
  • Priva TopControl Suite - Connect 8.7.8.0
  • Priva TopControl Suite - TPC 8.7.8.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-22-356-01 updated cvss 7.5

Priva TopControl Suite

  • Priva Bacnet < 8.7.8.0 Priva Blue ID < 8.7.8.0 Priva Compass < 8.7.8.0 Priva Connect < 8.7.8.0 Priva TPC < 8.7.8.0
    affected: vendor fix priva.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
18 mo ago

Exploit prediction

0.58% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected products

  • Priva TopControl Suite - Bacnet
  • Priva TopControl Suite - Blue ID
  • Priva TopControl Suite - Compass
  • Priva TopControl Suite - Connect
  • Priva TopControl Suite - TPC

Classification

Weakness
  • CWE-1391 Use of Weak Credentials
  • CWE-916 Use of Password Hash With Insufficient Computational Effort

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.