CVE-2017-3745

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
7.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: 0.4%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

In Lenovo XClarity Administrator (LXCA) before 1.3.0, if service data is downloaded from LXCA, a non-administrative user may have access to password information for users that have previously authenticated to the LXCA's internal LDAP server, including administrative accounts and service accounts with administrative privileges. This is an issue only for users who have used local authentication with LXCA and not remote authentication against external LDAP or ADFS servers.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

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

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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 20, 2017

Last Modified

June 17, 2026

References (1)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 21× 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 85 of 139 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. 15 repeat rows among the latest 100 are merged into the row they repeat. The 54 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2017-3745?
CVE-2017-3745 is a high-severity vulnerability; its CVE record was published on June 20, 2017. In Lenovo XClarity Administrator (LXCA) before 1.3.0, if service data is downloaded from LXCA, a non-administrative user may have access to password information for users that have previously authenticated to the LXCA's internal LDAP server, including administrative accounts and service accounts…
When was CVE-2017-3745 made public?
CVE-2017-3745 was made public on June 8, 2017: that is the date its CVE record's CNA, Lenovo Group Ltd., gives for when the vulnerability was made public. The CVE record itself was published on June 20, 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-3745 actively exploited?
CVE-2017-3745 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-3745?
CVE-2017-3745 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2017-3745?
A fix for CVE-2017-3745 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2017-3745?

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