CVE-2017-20025

CRITICALNVD 7.39.8
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-06-10. NVD baseline CVSS 7.3; sources differ by 2.5.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2017-11040 (ENISA EUVD) · GHSA-pgc3-76c4-r7v7 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS: 7.3Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

A vulnerability was found in Solare Solar-Log 2.8.4-56/3.5.2-85. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the component Flash Memory. The manipulation leads to privilege escalation. The attack can be launched remotely. Upgrading to version 3.5.3-86 is able to address this issue. It is recommended to upgrade the affected component.

CVSS v3
7.3
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.1%
EPSS %ILE
65th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

June 9, 2022

Last Modified

November 21, 2024

Advisory Details (1)

Auto-updated Oct 14, 2026
Fix named in the CVE record.
Web page

Full Disclosure: SEC Consult SA-20170322-0 :: Multiple vulnerabilities in Solare Datensysteme Solar-Log devices

http://seclists.org/fulldisclosure/2017/Mar/58

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 60× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 240 rows 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. None are among the latest 100 rows. The 140 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:27 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  2. 2026-11-12 11:20 UTCEchelonGraph re-scored
  3. 2026-11-12 11:20 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-11-11 16:29 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  5. 2026-11-11 12:56 UTCEchelonGraph re-scored
  6. 2026-11-11 12:56 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-11-10 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  8. 2026-11-10 14:32 UTCEchelonGraph re-scored
  9. 2026-11-10 14:32 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-11-09 16:27 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  11. 2026-11-09 16:08 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-11-08 17:42 UTCEchelonGraph re-scored
  13. 2026-11-08 17:42 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-11-08 16:29 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  15. 2026-11-07 19:18 UTCEchelonGraph re-scored
  16. 2026-11-07 19:18 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-11-07 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  18. 2026-11-06 20:50 UTCEchelonGraph re-scored
  19. 2026-11-06 20:50 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-11-06 16:28 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  21. 2026-11-05 22:26 UTCEchelonGraph re-scored
  22. 2026-11-05 22:26 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-11-05 16:28 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  24. 2026-11-05 00:00 UTCEchelonGraph re-scored
  25. 2026-11-05 00:00 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 75 more
  1. 2026-11-04 16:28 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  2. 2026-11-04 01:36 UTCEchelonGraph re-scored
  3. 2026-11-04 01:36 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-11-03 16:34 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  5. 2026-11-03 03:12 UTCEchelonGraph re-scored
  6. 2026-11-03 03:12 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-11-02 16:34 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  8. 2026-11-02 04:48 UTCEchelonGraph re-scored
  9. 2026-11-02 04:48 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-11-01 06:24 UTCEchelonGraph re-scored
  11. 2026-11-01 06:24 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-31 16:27 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  13. 2026-10-31 08:00 UTCEchelonGraph re-scored
  14. 2026-10-31 08:00 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-30 16:27 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  16. 2026-10-30 09:36 UTCEchelonGraph re-scored
  17. 2026-10-30 09:36 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-29 16:27 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  19. 2026-10-29 11:12 UTCEchelonGraph re-scored
  20. 2026-10-29 11:12 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-28 16:27 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  22. 2026-10-28 12:43 UTCEchelonGraph re-scored
  23. 2026-10-28 12:43 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-27 16:26 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  25. 2026-10-27 14:18 UTCEchelonGraph re-scored
  26. 2026-10-27 14:18 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-10-26 16:26 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  28. 2026-10-26 15:33 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  29. 2026-10-25 16:43 UTCEchelonGraph re-scored
  30. 2026-10-25 16:43 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-10-25 16:27 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  32. 2026-10-24 18:18 UTCEchelonGraph re-scored
  33. 2026-10-24 18:18 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  34. 2026-10-24 16:27 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  35. 2026-10-23 19:54 UTCEchelonGraph re-scored
  36. 2026-10-23 19:54 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  37. 2026-10-23 16:26 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  38. 2026-10-22 21:24 UTCEchelonGraph re-scored
  39. 2026-10-22 21:24 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  40. 2026-10-22 16:27 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  41. 2026-10-21 23:00 UTCEchelonGraph re-scored
  42. 2026-10-21 22:59 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-10-21 16:27 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  44. 2026-10-21 00:34 UTCEchelonGraph re-scored
  45. 2026-10-21 00:33 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-10-20 16:27 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  47. 2026-10-20 02:02 UTCEchelonGraph re-scored
  48. 2026-10-20 02:02 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-10-19 16:26 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  50. 2026-10-19 01:13 UTCEchelonGraph re-scored
  51. 2026-10-19 01:13 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-10-18 16:27 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  53. 2026-10-18 10:33 UTCEchelonGraph re-scored
  54. 2026-10-18 02:48 UTCEchelonGraph re-scored
  55. 2026-10-18 02:48 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-10-17 16:27 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  57. 2026-10-17 04:22 UTCEchelonGraph re-scored
  58. 2026-10-17 04:22 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-10-16 16:29 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  60. 2026-10-16 05:57 UTCEchelonGraph re-scored
  61. 2026-10-16 05:56 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-10-15 16:26 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  63. 2026-10-15 04:30 UTCEchelonGraph re-scored
  64. 2026-10-15 04:29 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-10-14 16:27 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  66. 2026-10-14 00:24 UTCEchelonGraph re-scored
  67. 2026-10-14 00:24 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-10-13 16:27 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  69. 2026-10-12 20:30 UTCGHSA enrichmentGHSA-pgc3-76c4-r7v7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-10-12 20:30 UTCEchelonGraph re-scored
  71. 2026-10-12 16:28 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  72. 2026-10-12 00:53 UTCEchelonGraph re-scored
  73. 2026-10-11 13:41 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  74. 2026-10-10 19:55 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
  75. 2026-10-09 20:02 UTCEPSS rescoreEPSS 1.1% · 63rd percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2017-20025?
CVE-2017-20025 is a critical-severity vulnerability; its CVE record was published on June 9, 2022. A vulnerability was found in Solare Solar-Log 2.8.4-56/3.5.2-85. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the component Flash Memory. The manipulation leads to privilege escalation. The attack can be launched remotely. Upgrading to version…
When was the CVE record for CVE-2017-20025 published?
The CVE record for CVE-2017-20025 was published on June 9, 2022. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2017-20025 actively exploited?
CVE-2017-20025 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (65th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-20025?
CVE-2017-20025 has a CVSS v3 base score of 7.3 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.8 (CRITICAL).
How do I remediate CVE-2017-20025?
The CVE record for CVE-2017-20025 names the fix: "Upgrading to version 3.5.3-86 is able to address this issue."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2017-20025?

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

Book a Demo →Browse All CVEs