Skip to content

Vendor

Ovarro vulnerabilities

12 published CVES affecting Ovarro, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
12
Critical
5
High
2
Medium
5
Low
0
Unscored
0
CISA KEV
0
Atom feed of Ovarro alerts

Products

Latest Ovarro CVEs

Newest publication first

  1. MediumCVSS 6.5 EPSS 0.32%

    All versions of the TWinSoft Configuration Tool store encrypted passwords as plaintext in memory. An attacker with access to system files could open a file to load the document into memory, including sensitive information associated with document, such as password. The attacker c...

  2. MediumCVSS 6.5 EPSS 0.51%

    The affected TBox RTUs allow low privilege users to access software security tokens of higher privilege. This could allow an attacker with “user” privileges to access files requiring higher privileges by establishing an SSH session and providing the other tokens.

  3. MediumCVSS 5.9 EPSS 0.51%

    The affected TBox RTUs generate software security tokens using insufficient entropy. The random seed used to generate the software tokens is not initialized correctly, and other parts of the token are generated using predictable time-based values. An attacker with this knowledge...

  4. CVE-2023-36607 CVE-2023-36607

    Published
    MediumCVSS 5.3 EPSS 0.49%

    The affected TBox RTUs are missing authorization for running some API commands. An attacker running these commands could reveal sensitive information such as software versions and web server file contents.

  5. CriticalCVSS 9.8 EPSS 1.4%

    The “ipk” package containing the configuration created by TWinSoft can be uploaded, extracted, and executed in Ovarro TBox, allowing malicious code execution.

  6. CriticalCVSS 9.8 EPSS 1.4%

    An attacker may use TWinSoft and a malicious source project file (TPG) to extract files on machine executing Ovarro TWinSoft, which could lead to code execution.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.