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

> Attackers can upload malicious files due to improper format checks, potentially leading to remote code execution.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **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:** 20 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3vfg-c25h-q774

## What is CVE-2019-14916?

CVE-2019-14916 is a medium-severity vulnerability in n/a, published on 20 Sep 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in PRiSE adAS 1.7.0. A file's format is not properly checked, leading to an unrestricted file upload.

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

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

It affects 1 product.


Products: Prise Adas.

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

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

## Is CVE-2019-14916 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-15088](https://insights.sbomify.com/CVE-2019-15088/): Auth bypass in n/a (critical 9.8)
- [CVE-2019-14914](https://insights.sbomify.com/CVE-2019-14914/): Path traversal in n/a (critical 9.1)
- [CVE-2019-15089](https://insights.sbomify.com/CVE-2019-15089/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2019-15085](https://insights.sbomify.com/CVE-2019-15085/): Information disclosure in n/a (high 7.5)
- [CVE-2019-15087](https://insights.sbomify.com/CVE-2019-15087/): Code injection in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-14916 is a medium-severity vulnerability in n/a, published on 20 Sep 2019. 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-14916 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-14916/ (Markdown: https://insights.sbomify.com/CVE-2019-14916/index.md)
```

## Sources

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

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