# CVE-2018-5204: File upload in ML Report

> Remote attackers can download and execute arbitrary files via the ActiveX method, leading to code execution on the victim's machine.

- **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:** 28 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-p56h-v253-6p88

## What is CVE-2018-5204?

CVE-2018-5204 is a critical vulnerability in Infraware ML Report, published on 28 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ML Report version Between 2.00.000.0000 and 2.18.628.5980 contains a vulnerability that could allow remote attacker to download and execute remote arbitrary file by setting the arguments to the activex method. this can be leveraged for code execution.

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

## Which versions are affected by CVE-2018-5204?

It affects 1 product.


Products: Infraware-Global Ml Report.

## How do I fix CVE-2018-5204?

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

## Is CVE-2018-5204 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-5204 and fix it if it is affected.

What it is: CVE-2018-5204 is a critical vulnerability in Infraware ML Report, published on 28 Dec 2018. 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-2018-5204 in the wild and no public exploit code.

Affected product: Infraware ML Report. 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-2018-5204/ (Markdown: https://insights.sbomify.com/CVE-2018-5204/index.md)
```

## Sources

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

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