# CVE-2017-17321: Memory corruption in eNSP

> A local attacker can exploit a buffer overflow in Huawei eNSP to cause the software process to crash, resulting in denial of service.

- **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **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:** 9 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-m2hw-pqrf-2xg8

## What is CVE-2017-17321?

CVE-2017-17321 is a low-severity memory corruption vulnerability in Huawei Technologies Co., Ltd. eNSP, published on 9 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Huawei eNSP software with software of versions earlier than V100R002C00B510 has a buffer overflow vulnerability. Due to the improper validation of specific command line parameter, a local attacker could exploit this vulnerability to cause the software process abnormal.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Huawei Ensp Firmware.

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

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

## Is CVE-2017-17321 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17321 is a low-severity memory corruption vulnerability in Huawei Technologies Co., Ltd. eNSP, published on 9 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-17321 in the wild and no public exploit code.

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

## Sources

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

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