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

> An attacker can upload arbitrary files via a vulnerable web API endpoint in Ivanti Endpoint Manager, potentially leading to remote code execution.

- **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:** 3 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-v9pf-4867-358f

## What is CVE-2019-12377?

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

### Official description

A vulnerable upl/async_upload.asp web API endpoint in Ivanti LANDESK Management Suite (LDMS, aka Endpoint Manager) 10.0.1.168 Service Update 5 allows arbitrary file upload, which may lead to arbitrary remote code execution.

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

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

It affects 1 product.


Products: Ivanti Landesk Management Suite.

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

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

## Is CVE-2019-12377 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-3147](https://insights.sbomify.com/CVE-2016-3147/): Memory corruption in n/a (critical 9.8)
- [CVE-2019-12373](https://insights.sbomify.com/CVE-2019-12373/): Information disclosure in n/a (critical 9.0)
- [CVE-2019-12374](https://insights.sbomify.com/CVE-2019-12374/): SQL injection in n/a (high 8.1)
- [CVE-2019-12375](https://insights.sbomify.com/CVE-2019-12375/): Path traversal in n/a (medium 6.3)
- [CVE-2019-12376](https://insights.sbomify.com/CVE-2019-12376/): Hardcoded credentials in n/a (medium 4.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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