# CVE-2017-15323: Denial of service in DP300,NIP6600,Secospace USG6500,TE60,TP3106,VP9660,ViewPoint 8660,ViewPoint 9030,eCNS210 TD,eSpace U1981

> Attackers can cause denial of service on Huawei network devices by sending malformed messages that exhaust memory due to insufficient input validation.

- **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:** 9 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jx9p-pjg4-8cmj

## What is CVE-2017-15323?

CVE-2017-15323 is a medium-severity denial of service vulnerability in Huawei Dp300 Firmware, 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 DP300 V500R002C00, NIP6600 V500R001C00, V500R001C20, V500R001C30, Secospace USG6500 V500R001C00, V500R001C20, V500R001C30, TE60 V100R001C01, V100R001C10, V100R003C00, V500R002C00, V600R006C00, TP3106 V100R001C06, V100R002C00, VP9660 V200R001C02, V200R001C30, V500R002C00, V500R002C10, ViewPoint 8660 V100R008C03, ViewPoint 9030 V100R011C02, V100R011C03, eCNS210_TD V100R004C10, eSpace U1981 V200R003C30 have a DoS vulnerability caused by memory exhaustion in some Huawei products. For lacking of adequate input validation, attackers can craft and send some malformed messages to the target device to exhaust the memory of the device and cause a Denial of Service (DoS).

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 10 products.


Products: Huawei Dp300 Firmware, Huawei Ecns210 Td Firmware, Huawei Espace U1981 Firmware, Huawei Nip6600 Firmware, Huawei Secospace Usg6500 Firmware, Huawei Te60 Firmware, Huawei Tp3106 Firmware, Huawei Viewpoint 8660 Firmware, Huawei Viewpoint 9030 Firmware, Huawei Vp9660 Firmware.

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

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

## Is CVE-2017-15323 being exploited?

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

## Other vulnerabilities in Huawei Dp300 Firmware

- [CVE-2017-2722](https://insights.sbomify.com/CVE-2017-2722/): Other in DP300,TE60,TP3106,ViewPoint 9030,eCNS210 TD,eSpace 7950,eSpace IAD,eSpace U1981 (high 8.8)
- [CVE-2017-17146](https://insights.sbomify.com/CVE-2017-17146/): Memory corruption in DP300 (high 7.8)
- [CVE-2017-17310](https://insights.sbomify.com/CVE-2017-17310/): Memory corruption in DP300, RP200, TE30, TE40, TE50, TE60 (high 7.5)
- [CVE-2017-15342](https://insights.sbomify.com/CVE-2017-15342/): Denial of service in DP300,TE60,TP3106,eSpace U1981 (high 7.5)
- [CVE-2017-17168](https://insights.sbomify.com/CVE-2017-17168/): Other in DP300, RP200, TE30, TE40, TE50, TE60, eSpace U1981 (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-15323 is a medium-severity denial of service vulnerability in Huawei Dp300 Firmware, 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-15323 in the wild and no public exploit code.

Affected product: Huawei Dp300 Firmware. 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-15323/ (Markdown: https://insights.sbomify.com/CVE-2017-15323/index.md)
```

## Sources

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

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