CVE Intelligence
Skip to main content
HIGH

CVE-2023-36609

CVE-2023-36609 Vulnerability Analysis & Exploit Intelligence

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.

Published Updated Sources: cvelistV5, icscert

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

1%

chance of exploitation in 30 days

Affects

ovarro

5 products listed

CVSS base

7.2

HIGH

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

ovarro

Products (5)

tbox ms cpu32tbox ms cpu32 s2tbox lt2tbox tg2tbox rm2

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
7.2CVSS 3.1HIGH——cvelistV5

Weakness & attack patterns

  • CWE-829

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1055Process Injection
  • T1195.001Supply Chain Compromise: Software Dependencies and Development Tools
  • T1505.005Server Software Component: Terminal Services DLL

References

1 on the record

Elsewhere on this site

  • ovarroevery CVE for this vendor
  • CWE-829other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.