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

> Authenticated users can upload malicious WAR files via path traversal in the file browser, leading to remote code execution with SYSTEM privileges.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jan 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3xw6-3pf3-2m73

## What is CVE-2019-14768?

CVE-2019-14768 is a high-severity vulnerability in n/a, published on 21 Jan 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An Arbitrary File Upload issue in the file browser of DIMO YellowBox CRM before 6.3.4 allows a standard authenticated user to deploy a new WebApp WAR file to the Tomcat server via Path Traversal, allowing remote code execution with SYSTEM privileges.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Dimo-Crm Yellowbox Crm.

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

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

## Is CVE-2019-14768 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-14765](https://insights.sbomify.com/CVE-2019-14765/): Missing authorization in n/a (high 8.8)
- [CVE-2019-14767](https://insights.sbomify.com/CVE-2019-14767/): Path traversal in n/a (high 7.5)
- [CVE-2019-14766](https://insights.sbomify.com/CVE-2019-14766/): Path traversal in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-14768 is a high-severity vulnerability in n/a, published on 21 Jan 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-14768 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-14768/ (Markdown: https://insights.sbomify.com/CVE-2019-14768/index.md)
```

## Sources

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

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