# CVE-2017-2717: Integer overflow in honor 8 Pro

> An attacker can cause a denial of service by sending a malformed response message that triggers an integer overflow and restarts the modem system.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 17 Sep 2024
- **Also known as:** GHSA-9mvf-47j3-995f

## What is CVE-2017-2717?

CVE-2017-2717 is a medium-severity vulnerability in Huawei Technologies Co., Ltd. honor 8 Pro, 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

honor 8 Pro with software Duke-L09C10B120 and earlier versions,Duke-L09C432B120 and earlier versions,Duke-L09C636B120 and earlier versions has an integer overflow vulnerability. The attacker sends a response message to the device, which contains an illegal length field, it could produce an integer overflow and restart the modem system.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Huawei Honor 8 Pro Firmware.

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

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

## Is CVE-2017-2717 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-2717 is a medium-severity vulnerability in Huawei Technologies Co., Ltd. honor 8 Pro, 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-2717 in the wild and no public exploit code.

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

## Sources

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

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