# CVE-2019-11031: File upload in n/a

> Attackers can upload malicious files via the auto-update service to execute arbitrary code with SYSTEM privileges on Mirasys VMS servers.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Aug 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cr87-f4jc-j7hc

## What is CVE-2019-11031?

CVE-2019-11031 is a critical vulnerability in n/a, published on 22 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Mirasys VMS before V7.6.1 and 8.x before V8.3.2 mishandles the auto-update feature of IDVRUpdateService2 in DVRServer.exe. An attacker can upload files with a Setup-Files action, and then execute these files with SYSTEM privileges.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2019-11031?

It affects 1 product.


Products: Mirasys Mirasys Vms.

## How do I fix CVE-2019-11031?

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

## Is CVE-2019-11031 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-11030](https://insights.sbomify.com/CVE-2019-11030/): Deserialization in n/a (critical 9.8)
- [CVE-2019-11029](https://insights.sbomify.com/CVE-2019-11029/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-11031 and fix it if it is affected.

What it is: CVE-2019-11031 is a critical vulnerability in n/a, published on 22 Aug 2019. 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-2019-11031 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-2019-11031/ (Markdown: https://insights.sbomify.com/CVE-2019-11031/index.md)
```

## Sources

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

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