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

> An attacker can upload arbitrary files to the Ruijie EG-2000 gateway due to improper input validation in the upload handler.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2024
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7wxh-vg3m-93vf

## What is CVE-2019-16640?

CVE-2019-16640 is a high-severity vulnerability in n/a, published on 16 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was found in upload.php on the Ruijie EG-2000 series gateway. A parameter passed to the class UploadFile is mishandled (%00 and /var/./html are not checked), which can allow an attacker to upload any file to the gateway. This affects EG-2000SE EG_RGOS 11.9 B11P1.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Ruijie Eg-2000se Firmware.

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

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

## Is CVE-2019-16640 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-16639](https://insights.sbomify.com/CVE-2019-16639/): Command injection in n/a (critical 9.8)
- [CVE-2019-16641](https://insights.sbomify.com/CVE-2019-16641/): Memory corruption in n/a (high 8.4)
- [CVE-2019-16638](https://insights.sbomify.com/CVE-2019-16638/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-16640 is a high-severity vulnerability in n/a, published on 16 Jul 2024. 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-2019-16640 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-2019-16640/ (Markdown: https://insights.sbomify.com/CVE-2019-16640/index.md)
```

## Sources

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

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