LiveActive security incident?Get immediate response
CVE Record

CVE-2023-36610: ​The affected TBox RTUs generate software security tokens using insufficient entropy.

​The affected TBox RTUs generate software security tokens using insufficient entropy. The random seed used to generate the software tokens is not initialized correctly, and other parts of the token are generated using predictable time-based values. An attacker with this knowledge could successfully brute force the token and authenticate themselves.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Certain Ovarro TBox RTUs can create authentication tokens from weak randomness and predictable time values. A knowledgeable attacker may be able to guess a valid token and authenticate. The impact is mainly confidentiality, with no integrity or availability impact identified in the supplied CVSS data.

Executive priority

Prioritize this for OT environments using Ovarro TBox RTUs, especially where remote access exists. The rating is moderate because exploitation is higher complexity and no active exploitation is cited, but successful authentication bypass could expose sensitive operational data.

Technical view

CVE-2023-36610 is CWE-331 in Ovarro TBox RTU software token generation. The random seed is not initialized correctly, and predictable time-based token components reduce entropy. CVSS 3.1 is 5.9, network reachable, no privileges or user interaction, high attack complexity, and high confidentiality impact.

Likely exposure

Exposure is most relevant to organizations operating the listed Ovarro TBox RTUs: MS-CPU32, MS-CPU32-S2, LT2, TG2, and RM2. Risk increases if management or authentication interfaces are reachable from untrusted networks. The supplied version data is incomplete and should be verified against vendor guidance.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Exploitation is described as brute forcing a predictable software token to authenticate, but CVSS rates attack complexity high. Treat this as credible OT authentication risk, not confirmed widespread exploitation.

Researcher notes

Evidence is limited to the CVE description, CVSS vector, affected product list, CWE-331, and CISA advisory reference. The bundle does not provide exact vulnerable firmware ranges, proof of exploitation, or named fixed versions. Avoid assuming broader Ovarro product impact without vendor confirmation.

Mitigation direction

  • Check CISA and Ovarro guidance for affected firmware and available fixes.
  • Inventory listed TBox RTUs and confirm deployed model and firmware versions.
  • Restrict RTU management access to trusted OT networks only.
  • Place exposed interfaces behind firewalls, VPNs, or jump hosts.
  • Monitor authentication activity for unusual failures or unexpected successful logins.

Validation and detection

  • Compare asset inventory against the affected Ovarro TBox RTU model list.
  • Verify whether any RTU authentication interfaces are reachable from untrusted networks.
  • Review vendor advisory status for firmware applicability and remediation instructions.
  • Check logs for abnormal authentication patterns or unknown administrative access.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-331: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-36610 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.9 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N2.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.9Medium
CVSS 3.1 vector shape for CVE-2023-36610Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
OvarroTBox MS-CPU320unaffected
Ovarro​TBox MS-CPU32-S20unaffected
OvarroTBox LT20unaffected
OvarroTBox TG20unaffected
OvarroTBox RM20unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-331 · source CWE mapping

Insufficient Entropy

Insufficient Entropy represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.