CVE-2017-5135

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-13. NVD baseline CVSS 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
9.1EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 18%CVSS: 9.1Exploit: Elevated riskExposed services: Not assessed

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

Certain Technicolor devices have an SNMP access-control bypass, possibly involving an ISP customization in some cases. The Technicolor (formerly Cisco) DPC3928SL with firmware D3928SL-P15-13-A386-c3420r55105-160127a could be reached by any SNMP community string from the Internet; also, you can write in the MIB because it provides write properties, aka Stringbleed. NOTE: the string-bleed/StringBleed-CVE-2017-5135 GitHub repository is not a valid reference as of 2017-04-27; it contains Trojan horse code purported to exploit this vulnerability.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
61
EG Risk 61/100CISA SSVC

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
Severity91% × 45%
Exploitation40% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
18%
EPSS %ILE
97th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (EG-KEV: elevated) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

April 27, 2017

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Aug 1, 2026
No fix on record yet.
generic

StringBleed

https://stringbleed.github.io/
generic

SecurityFocus

http://www.securityfocus.com/bid/98092

Data Freshness Timeline

(refreshed 4× in last 7d / 17× 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.

Showing the most recent 100 of 128 total refreshes for this CVE.

  1. 2026-10-05 17:38 UTCEPSS rescore
  2. 2026-10-03 14:21 UTCEPSS rescore
  3. 2026-09-30 14:59 UTCEPSS rescore
  4. 2026-09-30 09:34 UTCEG score recompute
  5. 2026-09-28 13:45 UTCEPSS rescore
  6. 2026-09-27 13:40 UTCEPSS rescore
  7. 2026-09-27 13:40 UTCEPSS rescore
  8. 2026-09-26 15:53 UTCEPSS rescore
  9. 2026-09-24 13:59 UTCEPSS rescore
  10. 2026-09-18 19:22 UTCEPSS rescore
  11. 2026-09-17 19:22 UTCEPSS rescore
  12. 2026-09-15 03:05 UTCEPSS rescore
  13. 2026-09-15 03:05 UTCEPSS rescore
  14. 2026-09-12 14:55 UTCEPSS rescore
  15. 2026-09-11 09:31 UTCEPSS rescore
  16. 2026-09-07 15:56 UTCEPSS rescore
  17. 2026-09-06 13:43 UTCEPSS rescore
  18. 2026-09-05 15:23 UTCEPSS rescore
  19. 2026-09-04 13:56 UTCEPSS rescore
  20. 2026-09-02 14:07 UTCEPSS rescore
  21. 2026-09-02 14:07 UTCEPSS rescore
  22. 2026-09-01 03:31 UTCEPSS rescore
  23. 2026-08-30 19:13 UTCEPSS rescore
  24. 2026-08-27 14:21 UTCEPSS rescore
  25. 2026-08-26 14:41 UTCEPSS rescore
Show 75 more
  1. 2026-08-25 13:44 UTCEPSS rescore
  2. 2026-08-21 23:44 UTCEPSS rescore
  3. 2026-08-20 22:51 UTCEPSS rescore
  4. 2026-08-19 16:59 UTCEPSS rescore
  5. 2026-08-18 13:43 UTCEPSS rescore
  6. 2026-08-16 14:51 UTCEPSS rescore
  7. 2026-08-16 02:10 UTCEPSS rescore
  8. 2026-08-15 01:26 UTCEPSS rescore
  9. 2026-08-12 13:46 UTCEPSS rescore
  10. 2026-08-07 16:22 UTCEPSS rescore
  11. 2026-08-06 13:42 UTCEPSS rescore
  12. 2026-08-05 19:12 UTCEPSS rescore
  13. 2026-08-04 15:05 UTCEPSS rescore
  14. 2026-08-01 04:11 UTCEPSS rescore
  15. 2026-07-30 16:24 UTCEPSS rescore
  16. 2026-07-28 15:32 UTCEPSS rescore
  17. 2026-07-26 14:51 UTCEPSS rescore
  18. 2026-07-23 14:15 UTCEPSS rescore
  19. 2026-07-23 01:29 UTCEG score recompute
  20. 2026-07-22 22:09 UTCEG score recompute
  21. 2026-07-22 14:04 UTCEPSS rescore
  22. 2026-07-22 14:04 UTCEPSS rescore
  23. 2026-07-21 15:21 UTCEPSS rescore
  24. 2026-07-21 15:21 UTCEPSS rescore
  25. 2026-07-20 17:04 UTCEPSS rescore
  26. 2026-07-19 02:26 UTCEPSS rescore
  27. 2026-07-19 02:26 UTCEPSS rescore
  28. 2026-07-18 10:00 UTCEPSS rescore
  29. 2026-07-16 16:59 UTCEPSS rescore
  30. 2026-07-16 16:59 UTCEPSS rescore
  31. 2026-07-15 16:54 UTCEPSS rescore
  32. 2026-07-15 01:56 UTCEPSS rescore
  33. 2026-07-15 01:56 UTCEPSS rescore
  34. 2026-07-13 22:26 UTCEPSS rescore
  35. 2026-07-12 05:43 UTCEPSS rescore
  36. 2026-07-11 08:24 UTCEPSS rescore
  37. 2026-07-09 19:06 UTCEPSS rescore
  38. 2026-07-08 15:10 UTCEPSS rescore
  39. 2026-07-07 13:42 UTCEPSS rescore
  40. 2026-07-06 16:24 UTCEPSS rescore
  41. 2026-07-06 16:24 UTCEPSS rescore
  42. 2026-07-05 02:27 UTCEPSS rescore
  43. 2026-07-04 06:28 UTCEPSS rescore
  44. 2026-07-02 16:54 UTCEPSS rescore
  45. 2026-07-01 15:02 UTCEPSS rescore
  46. 2026-06-30 23:19 UTCEPSS rescore
  47. 2026-06-30 23:19 UTCEPSS rescore
  48. 2026-06-29 14:03 UTCEPSS rescore
  49. 2026-06-28 14:04 UTCEPSS rescore
  50. 2026-06-28 04:53 UTCEPSS rescore
  51. 2026-06-27 03:06 UTCEPSS rescore
  52. 2026-06-27 03:05 UTCEPSS rescore
  53. 2026-06-25 13:47 UTCEPSS rescore
  54. 2026-06-24 14:02 UTCEPSS rescore
  55. 2026-06-24 14:02 UTCEPSS rescore
  56. 2026-06-23 21:30 UTCEPSS rescore
  57. 2026-06-21 14:54 UTCEPSS rescore
  58. 2026-06-21 14:54 UTCEPSS rescore
  59. 2026-06-21 01:57 UTCEPSS rescore
  60. 2026-06-21 01:57 UTCEPSS rescore
  61. 2026-06-19 19:23 UTCEPSS rescore
  62. 2026-06-19 19:23 UTCEPSS rescore
  63. 2026-06-18 17:50 UTCEPSS rescore
  64. 2026-06-17 17:50 UTCEPSS rescore
  65. 2026-06-16 17:50 UTCEPSS rescore
  66. 2026-06-16 17:50 UTCEPSS rescore
  67. 2026-06-15 17:45 UTCEPSS rescore
  68. 2026-06-14 23:14 UTCEPSS rescore
  69. 2026-06-13 22:57 UTCEPSS rescore
  70. 2026-06-12 23:09 UTCEPSS rescore
  71. 2026-06-10 22:15 UTCEPSS rescore
  72. 2026-06-10 13:19 UTCEPSS rescore
  73. 2026-06-06 13:45 UTCEPSS rescore
  74. 2026-06-06 13:45 UTCEPSS rescore
  75. 2026-06-05 22:44 UTCEPSS rescore

Publicly available exploits

(1 reference)

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

  • Exploit-DBEDB-43384
    First seen May 5, 2017

    Technicolor DPC3928SL - SNMP Authentication Bypass

    Open source ↗

Frequently asked(5)

What is CVE-2017-5135?
CVE-2017-5135 is a critical vulnerability published on April 27, 2017. Certain Technicolor devices have an SNMP access-control bypass, possibly involving an ISP customization in some cases. The Technicolor (formerly Cisco) DPC3928SL with firmware D3928SL-P15-13-A386-c3420r55105-160127a could be reached by any SNMP community string from the Internet; also, you can…
When was CVE-2017-5135 disclosed?
CVE-2017-5135 was first published on April 27, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-5135 actively exploited?
CVE-2017-5135 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 18% probability of exploitation in the next 30 days (97th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-5135?
CVE-2017-5135 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2017-5135?
No fix for CVE-2017-5135 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2017-5135?

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

Book a Demo →Browse All CVEs