CVE-2019-9760 in the critical feed json
FTPGetter Standard v.5.97.0.177 allows remote code execution when a user initiates an FTP connection to an attacker-controlled machine that…
published 7y ago modified 4mo ago also EUVD-2019-19123
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 53.1%
- EPSS 53.1% chance of exploitation in 30 days, percentile 98%
- public exploits
- 2
- Metasploit and Exploit-DB
Summary
FTPGetter Standard v.5.97.0.177 allows remote code execution when a user initiates an FTP connection to an attacker-controlled machine that sends crafted responses. Long responses can also crash the FTP client with memory corruption.
Is CVE-2019-9760 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
- First public exploit (Metasploit exploit/windows/ftp/ftpgetter_pwd_reply)
- Published
Exploit prediction
53.09% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/windows/ftp/ftpgetter_pwd_reply FTPGetter Standard v3.55.0.05 Stack Buffer Overflow (PWD) metasploit exploit, good rank, 2010-10-12
- EDB-46543 FTPGetter Standard 5.97.0.177 - Remote Code Execution remote, 2019-03-14
- github.com https://github.com/w4fz5uck5/FTPGetter/blob/master/xpl.py referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/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-787 Out-of-bounds Write
References
-
exploit-db.com
/exploits/46543/
exploit, third-party-advisory, vdb-entry
-
github.com
/w4fz5uck5/FTPGetter/blob/master/xpl.py
exploit, third-party-advisory
Sources
- CVE List CVE-2019-9760
- NVD CVE-2019-9760
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.