cve.bz

CVE-2017-8213 huawei smc2.0 firmware: Improper Certificate Validation

5.3 mediumEPSS 0.6%

Medium (5.3) in huawei smc2.0 firmware. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.0

5.3 medium
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 50th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-295 Improper Certificate Validation
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2017-8213 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-8213?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-8213?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2017-8213 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
huawei:smc2.0_firmwarev100r003c10
huawei:smc2.0_firmwarev100r005c00spc100
huawei:smc2.0_firmwarev100r005c00spc101b001t
huawei:smc2.0_firmwarev100r005c00spc102
huawei:smc2.0_firmwarev100r005c00spc103
huawei:smc2.0_firmwarev100r005c00spc200
huawei:smc2.0_firmwarev100r005c00spc201t
huawei:smc2.0_firmwarev500r002c00
huawei:smc2.0_firmwarev600r006c00

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON