CVE-2021-22646
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 · uneditedThe “ipk” package containing the configuration created by TWinSoft can be uploaded, extracted, and executed in Ovarro TBox, allowing malicious code execution.
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 confidenceOvarro TBox has a vulnerability where a malicious 'ipk' configuration package created by TWinSoft can be uploaded to the system, extracted, and executed. This allows arbitrary code execution with the privileges of the TBox process, potentially giving attackers full control over the industrial device.
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< 12.4< 1.46< 1.46< 1.46< 1.46< 1.46< 1.46< 1.46CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify TwinSoft version on the engineering workstationCheck the installed TwinSoft application version (typically in About or Help menu, or in Windows Programs and Features). Compare against the affected version range of < 12.4.Affected if TwinSoft version is below 12.4
-
Identify TBox firmware versionAccess the TBox device via its management interface or check the firmware version displayed on the device console/HMI. Compare against the affected version range of < 1.46.Affected if TBox firmware version is below 1.46 (applies to Lt2 530, Lt2 532, Lt2 540, Ms Cpu32, Ms Cpu32 S2, Rm2, Tg2 models)
-
Verify ipk package import functionality is accessibleCheck if the TBox device or TwinSoft project allows importing .ipk configuration packages. Look for package upload/import features in the management console or engineering software.Affected if ipk package import feature is enabled and accessible on the device or software
-
Audit recent ipk package importsReview TBox logs or TwinSoft project history for recent .ipk file imports. Check file system directories where ipk packages may be stored or extracted.Affected if Unknown or untrusted ipk packages have been recently imported to the system
You are affected if you run any TwinSoft version below 12.4 or any TBox firmware version below 1.46, and the ipk package import feature is accessible on your system.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.4612.4
Restrict ipk package uploads to only verified, trusted sources; implement network segmentation to isolate TBox devices; apply vendor patches when available; monitor for unauthorized configuration uploads.
Ovarro TBox firmware to version 1.46 or later; TwinSoft to version 12.4 or later
- 1. Identify the exact TBox device model (Lt2 530, Lt2 532, Lt2 540, Ms Cpu32, Ms Cpu32 S2, Rm2, or Tg2) currently deployed in your environment
- 2. Obtain the current firmware version of each TBox device by accessing the device's web interface or using TBox configuration tools
- 3. Download the TBox firmware version 1.46 or later from the official Ovarro (formerly B&R Automation) support portal
- 4. For TwinSoft SCADA/HMI software, download version 12.4 or later from the official Ovarro support portal
- 5. Back up all current TBox device configurations before performing firmware updates
- 6. Upload and apply the firmware 1.46 to each affected TBox device via the device's web interface or TBox firmware update utility
- 7. Update TwinSoft software to version 12.4 or later on all engineering workstations and servers
- 8. After updating, regenerate and redeploy ipk configuration packages using the updated TwinSoft version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22646 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-22646 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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