CVE-2009-4775 json
Format string vulnerability in Ipswitch WS_FTP Professional 12 before 12.2 allows remote attackers to cause a denial of service (crash) via…
published 16y ago modified 4mo ago also EUVD-2009-4738
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.6%
- EPSS 5.6% chance of exploitation in 30 days, percentile 92%
- public exploits
- 1
- Exploit-DB
Summary
Format string vulnerability in Ipswitch WS_FTP Professional 12 before 12.2 allows remote attackers to cause a denial of service (crash) via format string specifiers in the status code portion of an HTTP response.
Is CVE-2009-4775 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 (EDB-9607)
- Published
Exploit prediction
5.61% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-9607 Ipswitch WS_FTP 12 Professional - Remote Format String (PoC) dos, 2009-09-09
- packetstormsecurity.org http://www.packetstormsecurity.org/0909-exploits/nocoolnameforawsftppoc.pl.txt referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/36297 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-134 Use of Externally-Controlled Format String
References
-
exploit-db.com
/exploits/9607
exploit
-
packetstormsecurity.org
/0909-exploits/nocoolnameforawsftppoc.pl.txt
exploit
-
securityfocus.com
/bid/36297
vdb-entry, exploit
- docs.ipswitch.com /WS_FTP%20122/ReleaseNotes/English/index.htm?k_id=ipswitch_com_ftp_documents_worldwide_ws_ftp122releasenotesen
-
exchange.xforce.ibmcloud.com
/vulnerabilities/53098
vdb-entry
Sources
- CVE List CVE-2009-4775
- NVD CVE-2009-4775
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.