Skip to content
Fencer Vulns
high 8.8

CVE-2021-22646 json

Ovarro TBox Code Injection

published 2022-07-28 4 y ago modified 2026-06-17 4 mo ago also EUVD-2021-9782

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

Summary

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

Patch / fix

  • ovarro twinsoft 12.4
  • ovarro tbox_lt2-530_firmware 1.46
  • ovarro tbox_lt2-532_firmware 1.46
  • ovarro tbox_lt2-540_firmware 1.46
  • ovarro tbox_ms-cpu32_firmware 1.46
  • ovarro tbox_ms-cpu32-s2_firmware 1.46
  • ovarro tbox_rm2_firmware 1.46
  • ovarro tbox_tg2_firmware 1.46

Vendor advisories

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

cisa ICSA-21-054-04 updated cvss 8.8

Ovarro TBox (Update A)

  • Ovarro TBox MS-CPU32 < 12.4 (firmware 1.46) Ovarro TBox MS-CPU32-S2 < 12.4 (firmware 1.46) Ovarro TBox RM2 (All models) < 12.4 (firmware 1.46) Ovarro TBox TG2 (All models) < 12.4 (firmware 1.46) Ovarro TBoxLT2 (All models) < 12.4 (firmware 1.46)
    affected: mitigation “Ovarro recommends affected users update to 12.5 or later of TWinSoft to mitigate these vulnerabilities.” gcc02.safelinks.protection.outlook.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
no
Technical impact
total
Assessed
18 mo ago

Exploit prediction

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

CVSS scores

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

Affected products

  • Ovarro TBox

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code

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.