# CVE-2017-17132: Denial of service in VP9660

> An authenticated local attacker can cause a denial of service via a format string vulnerability in the license module logging.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Mar 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-78f6-722x-3325

## What is CVE-2017-17132?

CVE-2017-17132 is a medium-severity denial of service vulnerability in Huawei Technologies Co., Ltd. VP9660, published on 5 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Huawei VP9660 V500R002C10 has a uncontrolled format string vulnerability when the license module output the log information. An authenticated local attacker could exploit this vulnerability to cause a denial of service.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

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

It affects 1 product.


Products: Huawei Vp9660 Firmware.

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

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

## Is CVE-2017-17132 being exploited?

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

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

- [CVE-2017-17133](https://insights.sbomify.com/CVE-2017-17133/): Null dereference in VP9660 (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17132 is a medium-severity denial of service vulnerability in Huawei Technologies Co., Ltd. VP9660, published on 5 Mar 2018. 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-17132 in the wild and no public exploit code.

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

## Sources

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

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