CVE-2017-9861

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.4%CVSS: 9.8Exploit: None knownExposed services: Not assessed

No fix has been recorded since the CVE record was published in 2017 — if the vendor still supports the product, apply the fixed version it names; if not, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

An issue was discovered in SMA Solar Technology products. The SIP implementation does not properly use authentication with encryption: it is vulnerable to replay attacks, packet injection attacks, and man in the middle attacks. An attacker is able to successfully use SIP to communicate with the device from anywhere within the LAN. An attacker may use this to crash the device, stop it from communicating with the SMA servers, exploit known SIP vulnerabilities, or find sensitive information from the SIP communications. Furthermore, because the SIP communication channel is unencrypted, an attacker capable of understanding the protocol can eavesdrop on communications. For example, passwords can be extracted. NOTE: the vendor's position is that authentication with encryption is not required on an isolated subnetwork. Also, only Sunny Boy TLST-21 and TL-21 and Sunny Tripower TL-10 and TL-30 could potentially be affected

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
45
EG Risk 45/100

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 (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation1.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix has been recorded since the CVE record was published in 2017. If the vendor still supports the product, apply the fixed version it names within your standard update timelines; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.
EPSS PROB
1.4%
EPSS %ILE
72nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

No fix has been recorded since the CVE record was published in 2017. If the vendor still supports the product, apply the fixed version it names within your standard update timelines; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 5, 2017

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Oct 5, 2026
No fix on record since 2017.
Web page

CVE-Information for the 1.0 original horusscenario – Horus Scenario

https://horusscenario.com/CVE-information/

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 84 of 183 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 16 repeat rows among the latest 100 are merged into the row they repeat. The 99 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-15 16:27 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  2. 2026-10-15 11:53 UTCEG score recompute
  3. 2026-10-15 11:53 UTCGHSA enrichmentGHSA-9h99-58c3-vr7p · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-14 16:27 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  5. 2026-10-14 07:23 UTCEG score recompute
  6. 2026-10-14 07:23 UTCGHSA enrichmentGHSA-9h99-58c3-vr7p · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-13 16:27 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  8. 2026-10-13 02:38 UTCGHSA enrichmentGHSA-9h99-58c3-vr7p · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-12 20:23 UTCEG score recompute
  10. 2026-10-12 16:28 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  11. 2026-10-12 00:47 UTCEG score recompute
  12. 2026-10-11 13:41 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  13. 2026-10-10 19:55 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  14. 2026-10-09 20:02 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  15. 2026-10-08 16:36 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  16. 2026-10-07 23:41 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  17. 2026-10-06 15:12 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  18. 2026-10-05 17:39 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  19. 2026-10-03 14:21 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  20. 2026-09-30 14:59 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  21. 2026-09-30 09:49 UTCEG score recompute
  22. 2026-09-27 13:40 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  23. 2026-09-26 15:53 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  24. 2026-09-26 00:19 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  25. 2026-09-24 13:59 UTCEPSS rescoreEPSS 1.4% · 71st percentile
Show 59 more
  1. 2026-09-23 13:42 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  2. 2026-09-21 20:27 UTCEPSS rescoreEPSS 1.3% · 67th percentile
  3. 2026-09-20 20:09 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  4. 2026-09-19 15:36 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  5. 2026-09-17 19:22 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  6. 2026-09-15 03:05 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  7. 2026-09-13 16:42 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  8. 2026-09-12 14:56 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  9. 2026-09-11 09:31 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  10. 2026-09-07 15:56 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  11. 2026-09-05 15:24 UTCEPSS rescoreEPSS 1.3% · 66th percentile
  12. 2026-09-04 13:56 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  13. 2026-09-04 05:02 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  14. 2026-09-02 14:07 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  15. 2026-09-01 03:31 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  16. 2026-08-30 19:13 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  17. 2026-08-28 21:36 UTCEPSS rescoreEPSS 1.3% · 66th percentile
  18. 2026-08-27 14:21 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  19. 2026-08-26 14:41 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  20. 2026-08-25 13:44 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  21. 2026-08-23 00:14 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  22. 2026-08-21 23:44 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  23. 2026-08-19 16:59 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  24. 2026-08-18 13:43 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  25. 2026-08-16 14:51 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  26. 2026-08-16 02:10 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  27. 2026-08-15 01:26 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  28. 2026-08-12 13:46 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  29. 2026-08-09 13:42 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  30. 2026-08-08 16:32 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  31. 2026-08-07 16:22 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  32. 2026-08-06 13:42 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  33. 2026-08-05 19:13 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  34. 2026-08-02 02:23 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  35. 2026-08-01 04:12 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  36. 2026-07-30 16:24 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  37. 2026-07-30 01:26 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  38. 2026-07-28 15:32 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  39. 2026-07-26 14:51 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  40. 2026-07-23 14:15 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  41. 2026-07-23 01:31 UTCEG score recompute
  42. 2026-07-22 22:11 UTCEG score recompute
  43. 2026-07-22 14:04 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  44. 2026-07-21 15:21 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  45. 2026-07-20 17:04 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  46. 2026-07-19 14:28 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  47. 2026-07-19 02:26 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  48. 2026-07-18 10:01 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  49. 2026-07-16 16:59 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  50. 2026-07-15 16:54 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  51. 2026-07-15 01:56 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  52. 2026-07-13 22:26 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  53. 2026-07-12 05:43 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  54. 2026-07-11 08:24 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  55. 2026-07-09 19:06 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  56. 2026-07-08 15:11 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  57. 2026-07-06 16:24 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  58. 2026-07-06 02:20 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  59. 2026-07-05 02:27 UTCEPSS rescoreEPSS 1.4% · 69th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2017-9861?
CVE-2017-9861 is a critical-severity vulnerability; its CVE record was published on August 5, 2017. An issue was discovered in SMA Solar Technology products. The SIP implementation does not properly use authentication with encryption: it is vulnerable to replay attacks, packet injection attacks, and man in the middle attacks. An attacker is able to successfully use SIP to communicate with the…
When was CVE-2017-9861 made public?
CVE-2017-9861 was made public on August 5, 2017: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on August 5, 2017. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2017-9861 actively exploited?
CVE-2017-9861 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% probability of exploitation in the next 30 days (72nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-9861?
CVE-2017-9861 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-9861?
No fix for CVE-2017-9861 has been recorded since its CVE record was published in 2017. If the vendor still supports the product, apply the fixed version it names; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2017-9861?

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

Book a Demo →Browse All CVEs