CVE-2020-36617: A vulnerability was found in ewxrjk sftpserver

Q: How do I fix CVE-2020-36617?

sftpserver: upgrade to 2. Exact commands for each OS are on this page.

Q: Is CVE-2020-36617 being exploited?

CVE-2020-36617 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-36617 affect?

CVE-2020-36617 affects sftpserver. Severity is medium (CVSS 4.6). 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

Q: How urgent is CVE-2020-36617?

Priority 28/100. No elevated risk signals yet.

Routine

MEDIUM 4.6UPGRADE

CVE-2020-36617 is a medium-severity flaw (CVSS 4.6) affecting sftpserver. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.6 (Medium)
Attack vector	Adjacent network
Attack complexity	High
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.6% (top 52%)
CISA exploited list	No
Weakness	CWE-908
Published	2022-12-18
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: greenend

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-12-18 15:15 UTCPublished CVE record published
2026-06-17 03:15 UTCUpdated Record last modified

greenend sftpserver UPGRADE

Affected: < 2

Fixed in: 2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy sftpserver || rpm -q sftpserver || sftpserver --version

2. UPGRADE to 2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade sftpserver

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade sftpserver

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-36617?

sftpserver: upgrade to 2. Exact commands for each OS are on this page.

Is CVE-2020-36617 being exploited?

CVE-2020-36617 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-36617 affect?

CVE-2020-36617 affects sftpserver. Severity is medium (CVSS 4.6). 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

How urgent is CVE-2020-36617?

Priority 28/100. No elevated risk signals yet.

References

← Back to latest CVEs