Tbox Ms Cpu32 FirmwareOperating system · Ovarro

CVE-2023-36609

HIGH · 7.2 CVSS v3.1 Published 2023-07-03
Fix available
A fix is available. Upgrade to after 1.50.598 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
The affected TBox RTUs run OpenVPN with root privileges and can run user defined configuration scripts. An attacker could set up a local OpenVPN server and push a malicious script onto the TBox host to acquire root privileges.

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

TBox RTU devices run OpenVPN with root privileges and support user-defined configuration scripts. An attacker with local network access can set up a rogue OpenVPN server and push malicious scripts to the TBox device, which execute with root privileges allowing full system compromise.

MitigationRestrict network access to prevent unauthorized OpenVPN servers from connecting, disable or restrict user-defined configuration script execution, and reconfigure OpenVPN to run with least-privilege rather than root.

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
Tbox Ms Cpu32 FirmwareOperating system
Affected:<= 1.50.598
Tbox Ms Cpu32 S2 FirmwareOperating system
Affected:<= 1.50.598
Tbox Lt2 FirmwareOperating system
Affected:<= 1.50.598
Tbox Tg2 FirmwareOperating system
Affected:<= 1.50.598
Tbox Rm2 FirmwareOperating system
Affected:<= 1.50.598

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 the TBox device model
    Check the device label, firmware banner, or system information to confirm the model is one of: Ms Cpu32, Ms Cpu32 S2, Lt2, Tg2, or Rm2
    Affected if The device is an Ovarro TBox model from the affected product list
  2. Check the firmware version
    Access the device's web interface, CLI, or system info page and locate the firmware version number
    Affected if The firmware version is 1.50.598 or lower
  3. Verify OpenVPN is enabled
    Check the TBox configuration or running services to confirm OpenVPN is active on the device
    Affected if OpenVPN is enabled and running on the device
  4. Confirm OpenVPN runs as root
    Inspect the OpenVPN service configuration or process list to determine the user context (for example, check the OpenVPN init script or running process user)
    Affected if OpenVPN is running with root/privileged user rights rather than a restricted service account
  5. Check for user-defined script support
    Review the TBox OpenVPN configuration settings for any option allowing user-defined configuration scripts, custom scripts, or client script push capabilities
    Affected if User-defined configuration scripts or custom script execution is enabled or available in the OpenVPN setup
  6. Assess network exposure
    Examine network firewall rules, VLAN configuration, or access control lists to determine if the OpenVPN port (typically UDP/TCP 1194) is exposed to untrusted local network segments
    Affected if The device is on a network segment where unauthorized parties could establish a rogue OpenVPN server connection

The device is affected if it is an Ovarro TBox model (Ms Cpu32, Ms Cpu32 S2, Lt2, Tg2, or Rm2) running firmware <= 1.50.598, has OpenVPN enabled to run as root, and supports user-defined configuration scripts while being accessible to an untrusted local 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.

From vendor data
Upgrade available Upgrade to a release after 1.50.598
Interim mitigation

Restrict network access to prevent unauthorized OpenVPN servers from connecting, disable or restrict user-defined configuration script execution, and reconfigure OpenVPN to run with least-privilege rather than root.

Fix this in Tbox Ms Cpu32 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-36609 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-36609 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