# CVE-2021-42713: Information disclosure in n/a

> An attacker can read sensitive data from temporary files created by Splashtop Remote Client due to insecure directory permissions.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Feb 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-458p-jh3w-vf34

## What is CVE-2021-42713?

CVE-2021-42713 is a high-severity vulnerability in n/a, published on 15 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Splashtop Remote Client (Personal Edition) through 3.4.6.1 creates a Temporary File in a Directory with Insecure Permissions.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

## Which versions are affected by CVE-2021-42713?

It affects 1 product.


Products: Splashtop Splashtop.

## How do I fix CVE-2021-42713?

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

## Is CVE-2021-42713 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-42714](https://insights.sbomify.com/CVE-2021-42714/): Information disclosure in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-42713 and fix it if it is affected.

What it is: CVE-2021-42713 is a high-severity vulnerability in n/a, published on 15 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-42713 in the wild and no public exploit code.

Affected product: n/a. 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-2021-42713/ (Markdown: https://insights.sbomify.com/CVE-2021-42713/index.md)
```

## Sources

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

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