LiveActive security incident?Get immediate response
CVE Record

CVE-2021-22646: Ovarro TBox Code Injection

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

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-22646 affects Ovarro TBox devices where a TWinSoft-created configuration package can be uploaded, extracted, and executed. A user with low privileges could use this path to run malicious code, potentially impacting confidentiality, integrity, and availability of industrial control operations.

Executive priority

Treat this as a high-priority industrial control risk where affected TBox devices support operational processes. Prioritize exposure reduction and vendor-guided remediation, especially for remotely reachable management interfaces.

Technical view

The issue is code injection, classified as CWE-94. The CVSS 3.1 score is 8.8 with network access, low attack complexity, low privileges required, and no user interaction. Affected TBox versions listed are LT2, MS-CPU32, MS-CPU32-S2, RM2, and TG2.

Likely exposure

Exposure is most relevant where affected Ovarro TBox systems allow network access to package upload or configuration workflows, especially from broad enterprise or remote-access networks. The source bundle does not identify exposed internet prevalence.

Exploitation context

The provided data does not show CISA KEV listing or other cited evidence of active exploitation. The vulnerability is still high risk because exploitation requires only network access and low privileges, according to the CVSS vector.

Researcher notes

Evidence is limited to the CVE description, CVSS metadata, affected product list, CWE, and CISA advisory reference. No exploit status, patch version, or detailed mitigation is included in the supplied bundle, so remediation should be confirmed against vendor guidance.

Mitigation direction

  • Check Ovarro and CISA advisory guidance for affected-version remediation.
  • Restrict TBox management and package upload access to trusted administrators.
  • Segment affected TBox systems from enterprise and internet-facing networks.
  • Review accounts with upload or configuration privileges for least privilege.
  • Monitor for unexpected package uploads or configuration changes.

Validation and detection

  • Inventory Ovarro TBox LT2, MS-CPU32, MS-CPU32-S2, RM2, and TG2 deployments.
  • Confirm whether TWinSoft-created ipk package upload workflows are enabled or reachable.
  • Review device versions against the CISA and Ovarro advisory.
  • Check access controls for accounts allowed to upload configuration packages.
  • Look for recent unauthorized package uploads or configuration execution events.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-22646 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2021-22646Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
OvarroTBoxLT2, MS-CPU32, MS-CPU32-S2, RM2, TG2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.