# CVE-2023-45799: MLSoft TCO!stream Remote Code Execution Vulnerability

> An attacker can trick a victim into downloading and executing arbitrary files due to insufficient permission validation in MLSoft TCO!stream.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Oct 2023
- **Updated:** 6 Sep 2024
- **Also known as:** GHSA-pf23-jgjx-jcm5

## What is CVE-2023-45799?

CVE-2023-45799 is a high-severity code injection vulnerability in MLSoft TCO!stream, published on 30 Oct 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In MLSoft TCO!stream versions 8.0.22.1115 and below, a vulnerability exists due to insufficient permission validation. This allows an attacker to make the victim download and execute arbitrary files.

Weakness: CWE-494 (Download of Code Without Integrity Check)

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

It affects 1 product.


Products: Mlsoft Tco\!stream.

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

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

## Is CVE-2023-45799 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-45799 is a high-severity code injection vulnerability in MLSoft TCO!stream, published on 30 Oct 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-45799 in the wild and no public exploit code.

Affected product: MLSoft TCO!stream. 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-45799/ (Markdown: https://insights.sbomify.com/CVE-2023-45799/index.md)
```

## Sources

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

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