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

> Attackers can upload malicious files to Glory RBW-100 devices to execute code and gain root access.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/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:** 5 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9928-96cj-6hcq

## What is CVE-2019-10478?

CVE-2019-10478 is a high-severity vulnerability in n/a, published on 5 Apr 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered on Glory RBW-100 devices with firmware ISP-K05-02 7.0.0. An unrestricted file upload vulnerability in the Front Circle Controller glytoolcgi/settingfile_upload.cgi allows attackers to upload supplied data. This can be used to place attacker controlled code on the filesystem that can be executed and can lead to a reverse root shell.

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

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

It affects 1 product.


Products: Glory-Global Rbw-100 Firmware.

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

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

## Is CVE-2019-10478 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-10479](https://insights.sbomify.com/CVE-2019-10479/): Hardcoded credentials in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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