# CVE-2017-8213: Denial of service in SMC2.0

> Remote attackers can crash the TLS module in Huawei SMC2.0 by exploiting insufficient validation of PKI certificates during TLS and DTLS handshakes.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/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:** 22 Nov 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-484q-rm2r-3g72

## What is CVE-2017-8213?

CVE-2017-8213 is a medium-severity denial of service vulnerability in Huawei Technologies Co., Ltd. SMC2.0, published on 22 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Huawei SMC2.0 with software of V100R003C10, V100R005C00SPC100, V100R005C00SPC101B001T, V100R005C00SPC102, V100R005C00SPC103, V100R005C00SPC200, V100R005C00SPC201T, V500R002C00, V600R006C00 has an input validation vulnerability when handle TLS and DTLS handshake with certificate. Due to the insufficient validation of received PKI certificates, remote attackers could exploit this vulnerability to crash the TLS module.

Weakness: CWE-295 (Improper Certificate Validation)

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

It affects 1 product.


Products: Huawei Smc2.0 Firmware.

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

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

## Is CVE-2017-8213 being exploited?

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

## Other vulnerabilities in Huawei Technologies Co., Ltd. SMC2.0

- [CVE-2020-9209](https://insights.sbomify.com/CVE-2020-9209/): Privilege escalation in SMC2.0 (medium 6.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8213 is a medium-severity denial of service vulnerability in Huawei Technologies Co., Ltd. SMC2.0, published on 22 Nov 2017. 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-8213 in the wild and no public exploit code.

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

## Sources

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

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