filezilla vulnerabilities and fixes
Recent CVEs affecting filezilla, with upgrade or downgrade steps. 6 tracked.
filezilla has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 4. Most recent: 2007-04-26. Highest priority: CVE-2007-2318 (score 55/100).
- CVE-2007-2318 HIGH 9.3 UPGRADE Multiple format string vulnerabilities in FileZilla before 2.2.32 allow remote attackers to execute arbitrary
- CVE-2007-0317 HIGH 7.5 UPGRADE Format string vulnerability in the LogMessage function in FileZilla before 3.0.0-beta5 allows remote attackers
- CVE-2007-0315 HIGH 9.3 UPGRADE Multiple buffer overflows in FileZilla before 2.2.30a allow remote attackers to execute arbitrary code or caus
- CVE-2006-6564 MEDIUM 4.0 UPGRADE FileZilla Server before 0.9.22 allows remote attackers to cause a denial of service (crash) via a malformed ar
- CVE-2006-2403 HIGH 7.5 DOWNGRADE Buffer overflow in FileZilla before 2.2.23 allows remote attackers to execute arbitrary commands via unknown a
- CVE-2005-2898 MEDIUM 4.6 DOWNGRADE NOTE: this issue has been disputed by the vendor
FAQ
How do I fix filezilla vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is filezilla being exploited right now?
None of the tracked filezilla CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which filezilla CVE should I patch first?
CVE-2007-2318 currently ranks highest (55/100): Multiple format string vulnerabilities in FileZilla before 2.2.32 allow remote attackers to execute arbitrary .