CVE-2022-3010VulnerabilityPublished 2 Jan 2024Updated 4 Jun 2025

CVE-2022-3010: Priva TopControl Suite – Bacnet · Use of Weak Credentials

Affects Priva TopControl Suite – BacnetSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 8.7.8.0 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.7.8.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Priva TopControl Suite – Bacnet to 8.7.8.0.

Affected software

Product	Affected	Fixed in
Priva TopControl Suite - Bacnet	Affected <8.7.8.0	Fixed in 8.7.8.0

AI-suggested

Organizations should prioritize upgrading the Priva TopControl Suite to version 8.7.8.0 or later, where this vulnerability is presumably addressed. Until patching is possible, network-level mitigations should be implemented, including isolating the TopControl Suite devices on dedicated VLANs with strict access controls and firewall rules to limit SSH access only to trusted administrators. Employ network monitoring and anomaly detection to identify unauthorized SSH login attempts or unusual access patterns. If possible, disable SSH access or change default credentials to strong, unique passwords that do not derive from predictable information such as serial numbers. Implement multi-factor authentication for administrative access where supported. Conduct regular audits of device credentials and access logs. Additionally, organizations should review and enhance their asset inventory to identify all affected devices and ensure timely remediation. Vendor engagement for further guidance and monitoring for any emerging exploits is also recommended.

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.

Impact

For European organizations, this vulnerability poses a significant risk, particularly for those in sectors relying on building automation and critical infrastructure management, such as commercial real estate, healthcare, education, and government facilities. Unauthorized SSH access could lead to exposure of sensitive operational data, unauthorized changes to building control systems, or serve as a foothold for further attacks within the network. Given the high confidentiality impact, attackers could harvest credentials or system configurations, potentially leading to espionage or sabotage. The lack of required privileges or user interaction lowers the barrier for exploitation, increasing the threat level. Disruption or manipulation of building management systems could also indirectly affect availability of services or safety systems, although the vulnerability itself does not directly impact integrity or availability. European organizations with extensive deployments of Priva TopControl Suite are at risk of targeted attacks, especially in environments where network segmentation and monitoring are insufficient.

CWE-1391Use of Weak Credentials (opens in a new tab)
Class weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product uses weak credentials (such as a default key or hard-coded password) that can be calculated, derived, reused, or guessed by an attacker.
Architecture and Design · Operation
When the user changes or sets a password, check the password against a database of already compromised or breached passwords. These passwords are likely to be used in password guessing attacks.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Jul 2025, 07:11 UTC

WeaknessesCWE-1391

Technical details

References

Community reviews

Related threats