No exploitation reported

CVE-2017-17300

No exploitation reported by the sources we read.

Published2018-02-15
WeaknessCWE-20

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Huawei S12700 V200R008C00, V200R009C00, S5700 V200R007C00, V200R008C00, V200R009C00, S6700 V200R008C00, V200R009C00, S7700 V200R008C00, V200R009C00, S9700 V200R008C00, V200R009C00 have a numeric errors vulnerability. An unauthenticated, remote attacker may send specific TCP messages with keychain authentication option to the affected products. Due to the improper validation of the messages, it will cause numeric errors when handling the messages. Successful exploit will cause the affected products to reset.

Timeline

dates in UTC

2018-02-1516:29CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-17300?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-17300?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD

Huawei s5700 firmwareversion to verify

Branch	Affected	Fixed in	Source
200.x	= v200r007c00	no fix published	NVD
200.x	= v200r008c00	no fix published	NVD
200.x	= v200r009c00	no fix published	NVD

Huawei s12700 firmwareversion to verify

Branch	Affected	Fixed in	Source
200.x	= v200r008c00	no fix published	NVD
200.x	= v200r009c00	no fix published	NVD

Huawei s6700 firmwareversion to verify

Branch	Affected	Fixed in	Source
200.x	= v200r008c00	no fix published	NVD
200.x	= v200r009c00	no fix published	NVD

2 more products in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Advisories and patches

www.huawei.comVendor Advisory

Detection

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: none listed

Sources

NVDCVSS 3.07.5read 2026-10-23
NVDCVSS 2.07.8read 2026-10-23
NVDweakness (CWE)CWE-20read 2026-10-23
FIRST EPSSEPSS score1.6 %2026-10-22

Technical details

CVSS v3 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published: 2018-02-15
Last Modified: 2026-06-17
NVD status: Modified

Frequently asked questions

What is CVE-2017-17300?

Is CVE-2017-17300 actively exploited?

Active exploitation of CVE-2017-17300 has not been confirmed. Its EPSS score was 1.6% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2017-17300?

CVE-2017-17300 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database