# CVE-2020-12252: File upload in n/a

> Authenticated attackers can upload executable files to the web root, leading to remote code execution on Gigamon GigaVUE devices.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5pg6-jg49-4vj7

## What is CVE-2020-12252?

CVE-2020-12252 is a medium-severity vulnerability in n/a, published on 29 Apr 2020. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered in Gigamon GigaVUE 5.5.01.11. The upload functionality allows an arbitrary file upload for an authenticated user. If an executable file is uploaded into the www-root directory, then it could yield remote code execution via the filename parameter.

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

## Which versions are affected by CVE-2020-12252?

It affects 1 product.


Products: Gigamon Gigavue.

## How do I fix CVE-2020-12252?

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

## Is CVE-2020-12252 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-12251](https://insights.sbomify.com/CVE-2020-12251/): Path traversal in n/a (low 2.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-12252 and fix it if it is affected.

What it is: CVE-2020-12252 is a medium-severity vulnerability in n/a, published on 29 Apr 2020. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-12252 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-2020-12252/ (Markdown: https://insights.sbomify.com/CVE-2020-12252/index.md)
```

## Sources

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

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