No exploitation reported

CVE-2017-15317

No exploitation reported by the sources we read.

Published2017-12-22
WeaknessCWE-125

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

AR120-S V200R006C10, V200R007C00, V200R008C20, V200R008C30; AR1200 V200R006C10, V200R006C13, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30; AR1200-S V200R006C10, V200R007C00, V200R008C20, V200R008C30; AR150 V200R006C10, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30; AR150-S V200R006C10, V200R007C00, V200R008C20, V200R008C30; AR160 V200R006C10, V200R006C12, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30; AR200 V200R006C10, V200R007C00, V200R007C01, V200R008C20, V200R008C30; AR200-S V200R006C10, V200R007C00, V200R008C20, V200R008C30; AR2200 V200R006C10, V200R006C13, V200R006C16, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30; AR2200-S V200R006C10, V200R007C00, V200R008C20, V200R008C30; AR3200 V200R006C10, V200R006C11, V200R007C00, V200R007C01, V200R007C02, V200R008C00, V200R008C10, V200R008C20, V200R008C30; AR510 V200R006C10, V200R006C12, V200R006C13, V200R006C15, V200R006C16, V200R006C17, V200R007C00, V200R008C20, V200R008C30; SRG1300 V200R006C10, V200R007C00, V200R007C02, V200R008C20, V200R008C30; SRG2300 V200R006C10, V200R007C00, V200R007C02, V200R008C20, V200R008C30; SRG3300 V200R006C10, V200R007C00, V200R008C20, V200R008C30 have an input validation vulnerability in Huawei multiple products. Due to the insufficient input validation, an unauthenticated, remote attacker may craft a malformed Stream Control Transmission Protocol (SCTP) packet and send it to the device, causing the device to read out of bounds and restart.

Timeline

dates in UTC

2017-12-2217:29CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 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-15317?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-15317?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD

Huawei ar3200 firmwareversion to verify

Branch	Affected	Fixed in	Source
200.x	= v200r006c10	no fix published	NVD
200.x	= v200r006c11	no fix published	NVD
200.x	= v200r007c00	no fix published	NVD
200.x	= v200r007c01	no fix published	NVD
200.x	= v200r007c02	no fix published	NVD
200.x	= v200r008c00	no fix published	NVD
200.x	= v200r008c10	no fix published	NVD
200.x	= v200r008c20	no fix published	NVD
200.x	= v200r008c30	no fix published	NVD

Huawei ar510 firmwareversion to verify

Branch	Affected	Fixed in	Source
200.x	= v200r006c10	no fix published	NVD
200.x	= v200r006c12	no fix published	NVD
200.x	= v200r006c13	no fix published	NVD
200.x	= v200r006c15	no fix published	NVD
200.x	= v200r006c16	no fix published	NVD
200.x	= v200r006c17	no fix published	NVD
200.x	= v200r007c00	no fix published	NVD
200.x	= v200r008c20	no fix published	NVD
200.x	= v200r008c30	no fix published	NVD

Huawei ar2200 firmwareversion to verify

Branch	Affected	Fixed in	Source
200.x	= v200r006c10	no fix published	NVD
200.x	= v200r006c13	no fix published	NVD
200.x	= v200r006c16	no fix published	NVD
200.x	= v200r007c00	no fix published	NVD
200.x	= v200r007c01	no fix published	NVD
200.x	= v200r007c02	no fix published	NVD
200.x	= v200r008c20	no fix published	NVD
200.x	= v200r008c30	no fix published	NVD

12 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-125read 2026-10-23
FIRST EPSSEPSS score1.3 %2026-10-23

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: 2017-12-22
Last Modified: 2026-06-17
NVD status: Modified

Frequently asked questions

What is CVE-2017-15317?

Is CVE-2017-15317 actively exploited?

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

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

CVE-2017-15317 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