dbcve.org
TwinsoftApplication · Ovarro

CVE-2021-22642

HIGH · 7.5 CVSS v3.1 Published 2022-07-28
Fix available
A fix is available. Upgrade to 1.46 / 12.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An attacker could use specially crafted invalid Modbus frames to crash the Ovarro TBox system.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Ovarro TBox systems contain a vulnerability in their Modbus protocol parsing logic where specially crafted invalid Modbus frames can cause a system crash. The issue stems from improper handling of malformed Modbus requests, likely due to insufficient input validation or bounds checking in the protocol dissector.

MitigationApply vendor-supplied patches or firmware updates for the TBox system. If no patch is available, network segmentation and firewall rules should be implemented to restrict untrusted access to the Modbus interface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TwinsoftApplication
Affected:< 12.4
Tbox Lt2 530 FirmwareOperating system
Affected:< 1.46
Tbox Lt2 532 FirmwareOperating system
Affected:< 1.46
Tbox Lt2 540 FirmwareOperating system
Affected:< 1.46
Tbox Ms Cpu32 FirmwareOperating system
Affected:< 1.46
Tbox Ms Cpu32 S2 FirmwareOperating system
Affected:< 1.46
Tbox Rm2 FirmwareOperating system
Affected:< 1.46
Tbox Tg2 FirmwareOperating system
Affected:< 1.46

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Ovarro product type
    Determine if the system is running Ovarro Twinsoft software or one of the TBox device models (Lt2 530, Lt2 532, Lt2 540, Ms Cpu32, Ms Cpu32 S2, Rm2, Tg2). Check system inventory, device labeling, or software identification.
    Affected if The system is any Ovarro TBox hardware model or Twinsoft software.
  2. Check Twinsoft software version
    In the Twinsoft application interface, navigate to Help > About or check the installation directory for version information. Compare the version number against 12.4.
    Affected if Twinsoft version is below 12.4.
  3. Check TBox firmware version
    Access the TBox device via its management interface, console, or web interface. Look for firmware version information in the system settings or status page. Compare against version 1.46.
    Affected if TBox firmware version is below 1.46.
  4. Verify Modbus protocol is enabled
    Check the TBox or Twinsoft configuration for Modbus protocol settings. Look for Modbus TCP or RTU listeners, data point configurations using Modbus, or the Modbus dissector module being loaded.
    Affected if Modbus protocol parsing is enabled and the system is processing Modbus traffic.
  5. Assess Modbus network exposure
    Review network firewall rules, access control lists, or device network configuration to determine if the Modbus interface (typically port 502) is accessible from untrusted networks.
    Affected if Modbus interface is reachable from networks outside the trusted operational technology zone.

The environment is affected if it runs Ovarro Twinsoft below version 12.4 or any TBox firmware below version 1.46, with Modbus protocol enabled and network accessibility to the Modbus interface.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.46 / 12.4 or later
Fixed in 1.4612.4
Interim mitigation

Apply vendor-supplied patches or firmware updates for the TBox system. If no patch is available, network segmentation and firewall rules should be implemented to restrict untrusted access to the Modbus interface.

Recommended fix High confidence

Twinsoft version 12.4 or TBox firmware version 1.46 (depending on component)

  1. 1. Identify the specific TBox device model (Lt2 530, Lt2 532, Lt2 540, Ms Cpu32, Ms Cpu32 S2, Rm2, or Tg2) and current firmware version
  2. 2. Identify if Twinsoft configuration software is in use and determine its current version
  3. 3. Obtain the fixed firmware version 1.46 for TBox devices or Twinsoft version 12.4 from Ovarro's official support channels
  4. 4. Follow Ovarro's standard firmware update procedure for the specific TBox device model
  5. 5. Apply Twinsoft version 12.4 if the configuration software is in use
  6. 6. Verify the upgrade was successful by checking the firmware/software version
  7. 7. Test normal Modbus communications to ensure system stability

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Twinsoft Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-22642 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-22642 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data