# CVE-2017-2739: Supply chain in Vmall

> Attackers can intercept HTTP updates to implant malicious code in the Huawei Vmall mobile application, requiring users to upgrade to a secure version.

- **Severity:** Low 3.1 (`CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Nov 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-pw5x-8jcw-g7xj

## What is CVE-2017-2739?

CVE-2017-2739 is a low-severity vulnerability in Huawei Technologies Co., Ltd. Vmall, published on 22 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The upgrade package of Huawei Vmall APP Earlier than HwVmall 1.5.3.0 versions is transferred through HTTP. A man in the middle (MITM) can tamper with the upgrade package of Huawei Vmall APP, and to implant the malicious applications.

Weakness: CWE-494 (Download of Code Without Integrity Check)

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

It affects 1 product.


Products: Huawei Vmall.

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

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

## Is CVE-2017-2739 being exploited?

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

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

- [CVE-2017-8153](https://insights.sbomify.com/CVE-2017-8153/): Privilege escalation in VMall (for Android) (high 7.1)
- [CVE-2017-2694](https://insights.sbomify.com/CVE-2017-2694/): Missing authorization in HwVmall (low 3.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-2739 is a low-severity vulnerability in Huawei Technologies Co., Ltd. Vmall, published on 22 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-2739 in the wild and no public exploit code.

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

## Sources

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

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