# CVE-2014-8516: File upload in n/a

> Remote attackers can execute arbitrary code by uploading executable files to Visual Mining NetCharts Server.

- **Severity:** Critical 9.8 (`CVSS:3.1/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 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xffv-hvpr-87v7

## What is CVE-2014-8516?

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

### Official description

Unrestricted file upload vulnerability in Visual Mining NetCharts Server allows remote attackers to execute arbitrary code by uploading a file with an executable extension, then accessing it via unspecified vectors.

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

## Which versions are affected by CVE-2014-8516?

It affects 1 product.


Products: Cloudfastpath Netcharts Server.

## How do I fix CVE-2014-8516?

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

## Is CVE-2014-8516 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-8516 exists.

Public exploit code:

- Visual Mining NetCharts Server Remote Code Execution (metasploit)
- Visual Mining NetCharts Server - Remote Code Execution (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-8516 and fix it if it is affected.

What it is: CVE-2014-8516 is a critical vulnerability in n/a, published on 3 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-8516 exists.

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-2014-8516/ (Markdown: https://insights.sbomify.com/CVE-2014-8516/index.md)
```

## Sources

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

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