# CVE-2017-2737: File upload in VCM5010

> An authenticated attacker can upload arbitrary files to Huawei VCM5010 due to lack of validation, potentially leading to code execution.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 22 Nov 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-9wx5-w654-3m84

## What is CVE-2017-2737?

CVE-2017-2737 is a high-severity vulnerability in Huawei Technologies Co., Ltd. VCM5010, published on 22 Nov 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

VCM5010 with software versions earlier before V100R002C50SPC100 has an arbitrary file upload vulnerability. The software does not validate the files that uploaded. An authenticated attacker could upload arbitrary files to the system.

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

## Which versions are affected by CVE-2017-2737?

It affects 1 product.


Products: Huawei Vcm5010 Firmware.

## How do I fix CVE-2017-2737?

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

## Is CVE-2017-2737 being exploited?

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

## Other vulnerabilities in Huawei Technologies Co., Ltd. VCM5010

- [CVE-2017-2738](https://insights.sbomify.com/CVE-2017-2738/): Auth bypass in VCM5010 (critical 9.8)
- [CVE-2015-8332](https://insights.sbomify.com/CVE-2015-8332/): Privilege escalation in n/a (high 8.8)
- [CVE-2017-2736](https://insights.sbomify.com/CVE-2017-2736/): Command injection in VCM5010 (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-2737 and fix it if it is affected.

What it is: CVE-2017-2737 is a high-severity vulnerability in Huawei Technologies Co., Ltd. VCM5010, published on 22 Nov 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-2737 in the wild and no public exploit code.

Affected product: Huawei Technologies Co., Ltd. VCM5010. 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-2017-2737/ (Markdown: https://insights.sbomify.com/CVE-2017-2737/index.md)
```

## Sources

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

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