# CVE-2017-15333: Denial of service in S12700, S1700,S3700,S5700,S6700,S7700, S9700, eCNS210 TD

> Attackers can cause denial of service on Huawei network devices by sending specially crafted XML files to the vulnerable parser.

- **Severity:** Medium 4.7 (`CVSS:3.0/AV:L/AC:H/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-89wg-4vg7-4787

## What is CVE-2017-15333?

CVE-2017-15333 is a medium-severity denial of service vulnerability in Huawei Technologies Co., Ltd. S12700, S1700,S3700,S5700,S6700,S7700, S9700, eCNS210_TD, published on 15 Feb 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

XML parser in Huawei S12700 V200R005C00,S1700 V200R009C00, V200R010C00,S3700 V100R006C03, V100R006C05,S5700 V200R001C00, V200R002C00, V200R003C00, V200R003C02, V200R005C00, V200R006C00, V200R007C00, V200R008C00, V200R009C00, V200R010C00,S6700 V200R001C00, V200R002C00, V200R003C00, V200R005C00, V200R005C02, V200R008C00, V200R009C00, V200R010C00,S7700 V200R001C00, V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R007C00, V200R008C00, V200R009C00, V200R010C00,S9700 V200R001C00, V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R007C00, V200R008C00, V200R009C00, V200R010C00,eCNS210_TD V100R004C10, V100R004C10SPC003, V100R004C10SPC100, V100R004C10SPC101, V100R004C10SPC102, V100R004C10SPC200, V100R004C10SPC221, V100R004C10SPC400 has a DOS vulnerability. An attacker may craft specific XML files to the affected products. Due to not check the specially XML file and to parse this file, successful exploit will result in DOS attacks.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 7 products.


Products: Huawei Ecns210 Td Firmware, Huawei S12700 Firmware, Huawei S1700 Firmware, Huawei S5700 Firmware, Huawei S6700 Firmware, Huawei S7700 Firmware, Huawei S9700 Firmware.

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

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

## Is CVE-2017-15333 being exploited?

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

## Other vulnerabilities in Huawei Technologies Co., Ltd. S12700, S1700,S3700,S5700,S6700,S7700, S9700, eCNS210_TD

- [CVE-2017-15346](https://insights.sbomify.com/CVE-2017-15346/): Denial of service in S12700, S1700,S3700,S5700,S6700,S7700, S9700, eCNS210 TD (medium 4.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-15333 is a medium-severity denial of service vulnerability in Huawei Technologies Co., Ltd. S12700, S1700,S3700,S5700,S6700,S7700, S9700, eCNS210_TD, published on 15 Feb 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-15333 in the wild and no public exploit code.

Affected product: Huawei Technologies Co., Ltd. S12700, S1700,S3700,S5700,S6700,S7700, S9700, eCNS210_TD. 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-15333/ (Markdown: https://insights.sbomify.com/CVE-2017-15333/index.md)
```

## Sources

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

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