# CVE-2017-15353: Memory corruption in DP300,RP200,RSE6500,TE30,TE40,TE50,TE60,TX50,VP9660,ViewPoint 8660,ViewPoint 9030,Viewpoint 8660,

> An out-of-bounds read vulnerability in Huawei video conferencing devices allows attackers to cause service abnormalities via crafted messages.

- **Severity:** Low 3.7 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-53hw-g4w2-295x

## What is CVE-2017-15353?

CVE-2017-15353 is a low-severity memory corruption vulnerability in Huawei Dp300 Firmware, published on 15 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Huawei DP300, V500R002C00, RP200, V500R002C00, V600R006C00, RSE6500, V500R002C00, TE30, V100R001C02, V100R001C10, V500R002C00, V600R006C00, TE40, V500R002C00, V600R006C00, TE50, V500R002C00, V600R006C00, TE60, V100R001C01, V100R001C10, V500R002C00, V600R006C00, TX50, V500R002C00, V600R006C00, VP9660, V500R002C00, V500R002C10, ViewPoint 8660, V100R008C03, ViewPoint 9030, V100R011C02, V100R011C03, Viewpoint 8660, V100R008C03 have an out-of-bounds read vulnerability. An attacker has to control the peer device and send specially crafted messages to the affected products. Due to insufficient input validation, successful exploit may cause some service abnormal.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 11 products.


Products: Huawei Dp300 Firmware, Huawei Rp200 Firmware, Huawei Rse6500 Firmware, Huawei Te30 Firmware, Huawei Te40 Firmware, Huawei Te50 Firmware, Huawei Te60 Firmware, Huawei Tx50 Firmware, Huawei Viewpoint 8660 Firmware, Huawei Viewpoint 9030 Firmware, Huawei Vp9660 Firmware.

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

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

## Is CVE-2017-15353 being exploited?

There is no known exploitation of CVE-2017-15353 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-15353 and fix it if it is affected.

What it is: CVE-2017-15353 is a low-severity memory corruption vulnerability in Huawei Dp300 Firmware, published on 15 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-15353 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-15353/ (Markdown: https://insights.sbomify.com/CVE-2017-15353/index.md)
```

## Sources

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

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