dbcve.org
TwinsoftApplication · Ovarro

CVE-2021-22644

CRITICAL · 9.8 CVSS v3.1 Published 2022-07-28
Fix available
A fix is available. Upgrade to 1.46 / 12.4 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Ovarro TBox TWinSoft uses the custom hardcoded user “TWinSoft” with a hardcoded key.

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 · high confidence

Ovarro TBox TWinSoft uses a hardcoded username 'TWinSoft' with a hardcoded cryptographic key embedded in the software. This creates a backdoor that allows remote attackers to authenticate using these static credentials, potentially gaining full control of the TBox device and connected systems.

MitigationReplace the hardcoded credentials with unique, strong passwords or keys, disable the default TWinSoft account if possible, and ensure the TBox device is not directly exposed to untrusted networks.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 if Ovarro TWinSoft software is installed
    Check installed programs on Windows systems for 'TWinSoft' or review the program files directory where TWinSoft is typically installed. For TBox devices, access the device web interface or management console.
    Affected if TWinSoft software or TBox device is present in the environment
  2. Check TWinSoft or TBox firmware version
    In TWinSoft: go to Help > About or check the installed version in Programs and Features. For TBox devices: access the device status page or use the TBox management interface to view the firmware version.
    Affected if Version is below 12.4 for Twinsoft or below 1.46 for TBox firmware variants
  3. Verify if default TWinSoft account is enabled
    Access the user management or account settings within TWinSoft software or TBox device interface. Look for the built-in 'TWinSoft' user account and check its enabled status.
    Affected if The default TWinSoft user account exists and is active/enabled
  4. Check network exposure of TBox device or TWinSoft services
    Review firewall rules, network configurations, and any port exposures. Determine if the TBox device management interface or TWinSoft services are accessible from outside the trusted internal network.
    Affected if The TBox device or TWinSoft management interface is reachable from untrusted or public networks

The environment is affected if TWinSoft software below version 12.4 or any TBox firmware below 1.46 is running with the default TWinSoft account enabled and accessible from the network.

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

Replace the hardcoded credentials with unique, strong passwords or keys, disable the default TWinSoft account if possible, and ensure the TBox device is not directly exposed to untrusted networks.

Recommended fix Moderate confidence

Twinsoft 12.4; TBox firmware 1.46

  1. Upgrade Twinsoft to version 12.4 or later
  2. Upgrade Tbox Lt2 530 Firmware to version 1.46 or later
  3. Upgrade Tbox Lt2 532 Firmware to version 1.46 or later
  4. Upgrade Tbox Lt2 540 Firmware to version 1.46 or later
  5. Upgrade Tbox Ms Cpu32 Firmware to version 1.46 or later
  6. Upgrade Tbox Ms Cpu32 S2 Firmware to version 1.46 or later
  7. Upgrade Tbox Rm2 Firmware to version 1.46 or later
  8. Upgrade Tbox Tg2 Firmware to version 1.46 or later

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-22644 — 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-22644 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