CVE-2017-17215

CRITICALNVD 8.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 79% probability of exploitation within the next 30 days (top 0.5% of all CVEs). NVD baseline CVSS 8.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 78%
CISA-KEV: Not listedEPSS PROB: 78%CVSS: 8.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Huawei HG532 with some customized versions has a remote code execution vulnerability. An authenticated attacker could send malicious packets to port 37215 to launch attacks. Successful exploit could lead to the remote execution of arbitrary code.

CVSS v3
8.8
EG Score
9.0(high)
EG Risk
76(Track)
EG Risk 76/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation79% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
78%
EPSS %ILE
100%
KEV
Not listed

Published

March 20, 2018

Last Modified

November 21, 2024

Advisory Details (2)

Auto-updated Aug 16, 2026
No patch confirmed yet.
generic

SecurityFocus

http://www.securityfocus.com/bid/102344
generic

Security Notice - Statement on Remote Code Execution Vulnerability in Huawei HG532 Product

http://www.huawei.com/en/psirt/security-notices/huawei-sn-20171130-01-hg532-en

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 2× in last 7d / 14× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-04 05:01 UTCEPSS rescore
  2. 2026-09-01 13:48 UTCEPSS rescore
  3. 2026-08-30 19:13 UTCEPSS rescore
  4. 2026-08-28 21:36 UTCEPSS rescore
  5. 2026-08-26 14:41 UTCEPSS rescore
  6. 2026-08-25 13:44 UTCEPSS rescore
  7. 2026-08-24 14:10 UTCEPSS rescore
  8. 2026-08-21 23:44 UTCEPSS rescore
  9. 2026-08-20 22:50 UTCEPSS rescore
  10. 2026-08-19 16:59 UTCEPSS rescore
  11. 2026-08-16 14:51 UTCEPSS rescore
  12. 2026-08-16 02:10 UTCEPSS rescore
  13. 2026-08-15 01:26 UTCEPSS rescore
  14. 2026-08-13 21:56 UTCEPSS rescore
  15. 2026-08-07 16:22 UTCEPSS rescore
  16. 2026-08-06 13:42 UTCEPSS rescore
  17. 2026-08-05 19:12 UTCEPSS rescore
  18. 2026-08-03 10:30 UTCEPSS rescore
  19. 2026-08-02 02:23 UTCEPSS rescore
  20. 2026-07-30 16:24 UTCEPSS rescore
  21. 2026-07-30 01:26 UTCEPSS rescore
  22. 2026-07-26 14:51 UTCEPSS rescore
  23. 2026-07-23 01:28 UTCEG score recompute▲ 0.20
  24. 2026-07-22 22:07 UTCEG score recompute▼ 0.20
  25. 2026-07-22 14:04 UTCEPSS rescore
Show 33 more
  1. 2026-07-21 15:21 UTCEPSS rescore
  2. 2026-07-21 15:21 UTCEPSS rescore
  3. 2026-07-18 10:00 UTCEPSS rescore
  4. 2026-07-15 16:54 UTCEPSS rescore
  5. 2026-07-15 16:54 UTCEPSS rescore
  6. 2026-07-13 06:09 UTCEPSS rescore
  7. 2026-07-09 19:06 UTCEPSS rescore
  8. 2026-07-07 13:42 UTCEPSS rescore
  9. 2026-07-01 15:02 UTCEPSS rescore
  10. 2026-07-01 15:02 UTCEPSS rescore
  11. 2026-06-25 13:47 UTCEPSS rescore
  12. 2026-06-25 13:47 UTCEPSS rescore
  13. 2026-06-24 14:02 UTCEPSS rescore
  14. 2026-06-23 21:30 UTCEPSS rescore
  15. 2026-06-21 14:54 UTCEPSS rescore
  16. 2026-06-21 14:54 UTCEPSS rescore
  17. 2026-06-17 17:50 UTCEPSS rescore
  18. 2026-06-16 17:50 UTCEPSS rescore
  19. 2026-06-15 17:45 UTCEPSS rescore
  20. 2026-06-12 23:09 UTCEPSS rescore
  21. 2026-06-11 13:57 UTCEPSS rescore
  22. 2026-06-10 22:15 UTCEPSS rescore
  23. 2026-06-08 14:14 UTCEPSS rescore
  24. 2026-06-02 20:11 UTCEPSS rescore
  25. 2026-06-02 20:11 UTCEPSS rescore
  26. 2026-06-01 13:49 UTCEPSS rescore
  27. 2026-06-01 13:49 UTCEPSS rescore
  28. 2026-05-28 10:20 UTCEG score recompute
  29. 2026-05-28 10:20 UTCGHSA enrichment
  30. 2026-05-26 13:42 UTCEPSS rescore
  31. 2026-05-26 13:42 UTCEPSS rescore
  32. 2026-05-26 07:17 UTCEPSS rescore
  33. 2026-05-26 07:17 UTCEPSS rescore

Publicly available exploits

(3 references)

Working exploit code is in the public domain (2 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCwilfred-wulbou/HG532d-RCE-Exploit
    First seen Nov 17, 2020

    A Remote Code Execution (RCE) exploit for Huawei HG532d based on CVE-2017-17215 vulnerability. Modded from original PoC code from exploit-db.com

    Open source ↗
  • Exploit-DBEDB-43414
    First seen Dec 25, 2017

    Huawei Router HG532 - Arbitrary Command Execution

    Open source ↗
  • GitHub PoC1337g/CVE-2017-17215
    First seen Dec 25, 2017

    CVE-2017-17215 HuaWei Router RCE (NOT TESTED)

    Open source ↗

Frequently asked(5)

What is CVE-2017-17215?
CVE-2017-17215 is a critical vulnerability published on March 20, 2018. Huawei HG532 with some customized versions has a remote code execution vulnerability. An authenticated attacker could send malicious packets to port 37215 to launch attacks. Successful exploit could lead to the remote execution of arbitrary code.
When was CVE-2017-17215 disclosed?
CVE-2017-17215 was first published in the National Vulnerability Database on March 20, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-17215 actively exploited?
CVE-2017-17215 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 78% probability of exploitation in the next 30 days, which ranks it in the top 0.5% of all scored CVEs.
What is the CVSS score of CVE-2017-17215?
CVE-2017-17215 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2017-17215?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-17215, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-17215

Explore →

Is Your Infrastructure Affected by CVE-2017-17215?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs