# CVE-2023-36610: Weak cryptography in TBox LT2

> Attackers can brute force security tokens due to insufficient entropy in TBox RTUs, allowing unauthorized authentication and access to industrial control systems.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jul 2023
- **Updated:** 25 Oct 2024
- **Also known as:** GHSA-mp27-67w3-v3v9

## What is CVE-2023-36610?

CVE-2023-36610 is a medium-severity vulnerability in Ovarro TBox LT2, published on 3 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

​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.

Weakness: CWE-331 (Insufficient Entropy)

## Which versions are affected by CVE-2023-36610?

It affects 5 products.


Products: Ovarro Tbox Lt2 Firmware, Ovarro Tbox Ms-Cpu32-S2 Firmware, Ovarro Tbox Ms-Cpu32 Firmware, Ovarro Tbox Rm2 Firmware, Ovarro Tbox Tg2 Firmware.

## How do I fix CVE-2023-36610?

No fix has been published for CVE-2023-36610 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-36610 being exploited?

There is no known exploitation of CVE-2023-36610 in the wild and no public exploit code.

## Other vulnerabilities in Ovarro TBox LT2

- [CVE-2023-36609](https://insights.sbomify.com/CVE-2023-36609/): Code injection in TBox LT2 (high 7.2)
- [CVE-2023-3395](https://insights.sbomify.com/CVE-2023-3395/): Information disclosure in TBox LT2 (medium 6.5)
- [CVE-2023-36608](https://insights.sbomify.com/CVE-2023-36608/): Weak cryptography in TBox LT2 (medium 6.5)
- [CVE-2023-36611](https://insights.sbomify.com/CVE-2023-36611/): Privilege escalation in TBox LT2 (medium 6.5)
- [CVE-2023-36607](https://insights.sbomify.com/CVE-2023-36607/): CVE-2023-36607 (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-36610 and fix it if it is affected.

What it is: CVE-2023-36610 is a medium-severity vulnerability in Ovarro TBox LT2, published on 3 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-36610 in the wild and no public exploit code.

Affected product: Ovarro TBox LT2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-36610/ (Markdown: https://insights.sbomify.com/CVE-2023-36610/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-36610
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-36610
- OSV: https://osv.dev/vulnerability/CVE-2023-36610

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-36610/
Summaries are generated and may contain mistakes; the official description above is the record.