# CVE-2023-3395: Information disclosure in TBox LT2

> Attackers with local file access can extract plaintext passwords from memory when opening documents in TWinSoft Configuration Tool.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jul 2023
- **Updated:** 24 Oct 2024
- **Also known as:** GHSA-mj3g-5jvr-4w7h

## What is CVE-2023-3395?

CVE-2023-3395 is a medium-severity vulnerability in Ovarro TBox LT2, published on 3 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

​All versions of the TWinSoft Configuration Tool store encrypted passwords as plaintext in memory. An attacker with access to system files could open a file to load the document into memory, including sensitive information associated with document, such as password. The attacker could then obtain the plaintext password by using a memory viewer.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information), CWE-256 (Plaintext Storage of a Password)

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

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-3395?

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

## Is CVE-2023-3395 being exploited?

There is no known exploitation of CVE-2023-3395 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-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-36610](https://insights.sbomify.com/CVE-2023-36610/): Weak cryptography in TBox LT2 (medium 5.9)
- [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-3395 and fix it if it is affected.

What it is: CVE-2023-3395 is a medium-severity vulnerability in Ovarro TBox LT2, published on 3 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-3395 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-3395/ (Markdown: https://insights.sbomify.com/CVE-2023-3395/index.md)
```

## Sources

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

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