How severe is CVE-2017-8213?

CVE-2017-8213 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability low.

Is CVE-2017-8213 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (45th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2017-8213?

CVE-2017-8213 primarily affects Huawei Smc2.0 Firmware. In total, 9 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2017-8213?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2017-8213 published?

CVE-2017-8213 was published on 2017-11-22 and last updated on 2026-06-17.

CVE-2017-8213

CVE-2017-8213 is a medium-severity vulnerability in Huawei Smc2.0 Firmware with a CVSS 3.x base score of 5.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-295.

Key facts

Severity: Medium (CVSS 3.x base score 5.3)
CVSS v2: 5.0
EPSS exploit prediction: 1% (45th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-295
Affected product: Huawei Smc2.0 Firmware
Published: 2017-11-22
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2017-8213?: 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.
How severe is CVE-2017-8213?: CVE-2017-8213 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability low.
Is CVE-2017-8213 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (45th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-8213?: CVE-2017-8213 primarily affects Huawei Smc2.0 Firmware. In total, 9 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2017-8213?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2017-8213 published?: CVE-2017-8213 was published on 2017-11-22 and last updated on 2026-06-17.

References

http://www.huawei.com/en/psirt/security-advisories/huawei-sa-20170705-01-tls-en

Affected products (9)

cpe:2.3:o:huawei:smc2.0_firmware:v100r003c10:*:*:*:*:*:*:*
cpe:2.3:o:huawei:smc2.0_firmware:v100r005c00spc100:*:*:*:*:*:*:*
cpe:2.3:o:huawei:smc2.0_firmware:v100r005c00spc101b001t:*:*:*:*:*:*:*
cpe:2.3:o:huawei:smc2.0_firmware:v100r005c00spc102:*:*:*:*:*:*:*
cpe:2.3:o:huawei:smc2.0_firmware:v100r005c00spc103:*:*:*:*:*:*:*
cpe:2.3:o:huawei:smc2.0_firmware:v100r005c00spc200:*:*:*:*:*:*:*
cpe:2.3:o:huawei:smc2.0_firmware:v100r005c00spc201t:*:*:*:*:*:*:*
cpe:2.3:o:huawei:smc2.0_firmware:v500r002c00:*:*:*:*:*:*:*
cpe:2.3:o:huawei:smc2.0_firmware:v600r006c00:*:*:*:*:*:*:*

More vulnerabilities in Huawei Smc2.0 Firmware

CVE-2019-0708 — Critical (CVSS 9.8): A remote code execution vulnerability exists in Remote Desktop Services formerly known as Terminal Services when an…
CVE-2017-17301 — Critical (CVSS 9.8): Huawei AR120-S V200R005C32, V200R006C10, V200R007C00, V200R008C20, AR1200 V200R005C20, V200R005C32, V200R006C10,…
CVE-2021-22299 — High (CVSS 7.8): There is a local privilege escalation vulnerability in some Huawei products. A local, authenticated attacker could…
CVE-2019-19417 — High (CVSS 7.5): The SIP module of some Huawei products have a denial of service (DoS) vulnerability. A remote attacker could exploit…
CVE-2019-19416 — High (CVSS 7.5): The SIP module of some Huawei products have a denial of service (DoS) vulnerability. A remote attacker could exploit…
CVE-2019-19415 — High (CVSS 7.5): The SIP module of some Huawei products have a denial of service (DoS) vulnerability. A remote attacker could exploit…

All CVEs affecting Huawei Smc2.0 Firmware →

Other CWE-295 (Improper Certificate Validation) vulnerabilities

CVE-2026-4370 — Critical (CVSS 10.0): A vulnerability was identified in Juju from version 3.2.0 until 3.6.19 and from version 4.0 until 4.0.4, where the…
CVE-2026-30836 — Critical (CVSS 10.0): Step CA is an online certificate authority for secure, automated certificate management for DevOps. Versions 0.30.0-rc6…
CVE-2025-68121 — Critical (CVSS 10.0): During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between…
CVE-2022-20703 — Critical (CVSS 10.0): Multiple vulnerabilities in Cisco Small Business RV160, RV260, RV340, and RV345 Series Routers could allow an attacker…
CVE-2021-1471 — Critical (CVSS 9.9): Multiple vulnerabilities in Cisco Jabber for Windows, Cisco Jabber for MacOS, and Cisco Jabber for mobile platforms…
CVE-2026-20184 — Critical (CVSS 9.8): A vulnerability in the integration of single sign-on (SSO) with Control Hub in Cisco Webex Services could have allowed…

Browse all CWE-295 (Improper Certificate Validation) vulnerabilities →