CVE-2020-36617

MEDIUMNVD 4.69.8▲
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-12-18. NVD baseline CVSS 4.6; sources differ by 5.2.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.6
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 4.6Exploit: NoneExposed: 0

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

A vulnerability was found in ewxrjk sftpserver. It has been declared as problematic. Affected by this vulnerability is the function sftp_parse_path of the file parse.c. The manipulation leads to uninitialized pointer. The real existence of this vulnerability is still doubted at the moment. The name of the patch is bf4032f34832ee11d79aa60a226cc018e7ec5eed. It is recommended to apply a patch to fix this issue. The identifier VDB-216205 was assigned to this vulnerability. NOTE: In some deployment models this would be a vulnerability. README specifically warns about avoiding such deployment models.

CVSS v3
4.6
EG Score
9.8(medium)
EPSS
42.0%
KEV
Not listed

Published

December 18, 2022

Last Modified

November 21, 2024

References (4)

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 43× 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-07-15 16:55 UTCEPSS rescore
  2. 2026-07-15 16:55 UTCEPSS rescore
  3. 2026-07-15 01:57 UTCEPSS rescore
  4. 2026-07-13 22:27 UTCEPSS rescore
  5. 2026-07-13 22:27 UTCEPSS rescore
  6. 2026-07-13 06:10 UTCEPSS rescore
  7. 2026-07-13 06:10 UTCEPSS rescore
  8. 2026-07-12 05:44 UTCEPSS rescore
  9. 2026-07-11 08:25 UTCEPSS rescore
  10. 2026-07-11 08:25 UTCEPSS rescore
  11. 2026-07-09 19:07 UTCEPSS rescore
  12. 2026-07-08 15:12 UTCEPSS rescore
  13. 2026-07-07 13:43 UTCEPSS rescore
  14. 2026-07-06 16:25 UTCEPSS rescore
  15. 2026-07-06 16:25 UTCEPSS rescore
  16. 2026-07-06 02:21 UTCEPSS rescore
  17. 2026-07-06 02:21 UTCEPSS rescore
  18. 2026-07-04 06:29 UTCEPSS rescore
  19. 2026-07-04 06:29 UTCEPSS rescore
  20. 2026-06-30 23:20 UTCEPSS rescore
  21. 2026-06-30 23:20 UTCEPSS rescore
  22. 2026-06-29 14:04 UTCEPSS rescore
  23. 2026-06-28 11:19 UTCOSV refresh
  24. 2026-06-28 04:54 UTCEPSS rescore
  25. 2026-06-28 04:54 UTCEPSS rescore
Show 56 more
  1. 2026-06-27 03:06 UTCEPSS rescore
  2. 2026-06-27 03:06 UTCEPSS rescore
  3. 2026-06-25 13:48 UTCEPSS rescore
  4. 2026-06-24 14:03 UTCEPSS rescore
  5. 2026-06-24 14:03 UTCEPSS rescore
  6. 2026-06-23 21:31 UTCEPSS rescore
  7. 2026-06-23 21:31 UTCEPSS rescore
  8. 2026-06-22 14:23 UTCEPSS rescore
  9. 2026-06-22 14:23 UTCEPSS rescore
  10. 2026-06-21 14:54 UTCEPSS rescore
  11. 2026-06-21 14:54 UTCEPSS rescore
  12. 2026-06-21 01:57 UTCEPSS rescore
  13. 2026-06-19 19:24 UTCEPSS rescore
  14. 2026-06-19 19:23 UTCEPSS rescore
  15. 2026-06-18 17:50 UTCEPSS rescore
  16. 2026-06-18 17:50 UTCEPSS rescore
  17. 2026-06-17 17:50 UTCEPSS rescore
  18. 2026-06-16 17:50 UTCEPSS rescore
  19. 2026-06-15 17:46 UTCEPSS rescore
  20. 2026-06-14 23:15 UTCEPSS rescore
  21. 2026-06-13 22:58 UTCEPSS rescore
  22. 2026-06-12 23:10 UTCEPSS rescore
  23. 2026-06-11 13:58 UTCEPSS rescore
  24. 2026-06-10 22:16 UTCEPSS rescore
  25. 2026-06-10 21:17 UTCOSV refresh
  26. 2026-06-10 13:20 UTCEPSS rescore
  27. 2026-06-08 14:15 UTCEPSS rescore
  28. 2026-06-07 15:23 UTCEPSS rescore
  29. 2026-06-07 15:23 UTCEPSS rescore
  30. 2026-06-07 15:23 UTCEPSS rescore
  31. 2026-06-06 13:46 UTCEPSS rescore
  32. 2026-06-06 13:45 UTCEPSS rescore
  33. 2026-06-05 22:45 UTCEPSS rescore
  34. 2026-06-05 22:45 UTCEPSS rescore
  35. 2026-06-05 06:08 UTCEPSS rescore
  36. 2026-06-05 06:08 UTCEPSS rescore
  37. 2026-06-04 13:10 UTCEPSS rescore
  38. 2026-06-04 13:10 UTCEPSS rescore
  39. 2026-06-02 20:11 UTCEPSS rescore
  40. 2026-06-02 20:11 UTCEPSS rescore
  41. 2026-06-01 13:50 UTCEPSS rescore
  42. 2026-05-31 22:29 UTCEPSS rescore
  43. 2026-05-31 22:29 UTCEPSS rescore
  44. 2026-05-31 00:15 UTCEPSS rescore
  45. 2026-05-31 00:15 UTCEPSS rescore
  46. 2026-05-29 13:42 UTCEPSS rescore
  47. 2026-05-28 13:43 UTCEPSS rescore
  48. 2026-05-28 13:43 UTCEPSS rescore
  49. 2026-05-27 13:39 UTCEPSS rescore
  50. 2026-05-27 13:39 UTCEPSS rescore
  51. 2026-05-26 13:42 UTCEPSS rescore
  52. 2026-05-26 13:42 UTCEPSS rescore
  53. 2026-05-26 07:17 UTCEPSS rescore
  54. 2026-05-26 07:17 UTCEPSS rescore
  55. 2026-05-25 10:17 UTCEG score recompute
  56. 2026-05-25 10:17 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2020-36617?
CVE-2020-36617 is a medium vulnerability published on December 18, 2022. A vulnerability was found in ewxrjk sftpserver. It has been declared as problematic. Affected by this vulnerability is the function sftpparsepath of the file parse.c. The manipulation leads to uninitialized pointer. The real existence of this vulnerability is still doubted at the moment. The name…
When was CVE-2020-36617 disclosed?
CVE-2020-36617 was first published in the National Vulnerability Database on December 18, 2022, 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-2020-36617 actively exploited?
CVE-2020-36617 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 42.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2020-36617?
CVE-2020-36617 has a CVSS v3 base score of 4.6 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.8.
How do I remediate CVE-2020-36617?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-36617, 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-2020-36617

Explore →

Is Your Infrastructure Affected by CVE-2020-36617?

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

Start Free Scan →Browse All CVEs