CVE-2020-20277 in the critical feed json
There are multiple unauthenticated directory traversal vulnerabilities in different FTP commands in uftpd FTP server versions 2.7 to 2.10 d…
published 5y ago modified 4mo ago also EUVD-2020-13064
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 26.2%
- EPSS 26.2% chance of exploitation in 30 days, percentile 98%
- public exploits
- 1
- Exploit-DB
Summary
There are multiple unauthenticated directory traversal vulnerabilities in different FTP commands in uftpd FTP server versions 2.7 to 2.10 due to improper implementation of a chroot jail in common.c's compose_abspath function that can be abused to read or write to arbitrary files on the filesystem, leak process memory, or potentially lead to remote code execution.
Patch / fix
Is CVE-2020-20277 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- Published
- First public exploit (EDB-51000)
Exploit prediction
26.24% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-51000 uftpd 2.10 - Directory Traversal (Authenticated) remote, 2022-08-02
- packetstormsecurity.com http://packetstormsecurity.com/files/167908/uftpd-2.10-Directory-Traversal.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/troglobit/uftpd/commit/455b47d3756aed162d2d0ef7f40b549f3b5b30fe
patch, third-party-advisory
-
packetstormsecurity.com
/files/167908/uftpd-2.10-Directory-Traversal.html
exploit, third-party-advisory, vdb-entry
-
arinerron.com
/blog/posts/6
third-party-advisory
Sources
- CVE List CVE-2020-20277
- NVD CVE-2020-20277
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.