CVE-2009-5012

CVE-2009-5012 is a high-severity security vulnerability in pyftpdlib (pip), affecting versions <= 0.5.1. It is fixed in 0.5.2.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Improper Access Control in pyftpdlib

ftpserver.py in pyftpdlib before 0.5.2 does not require the l permission for the MLST command, which allows remote authenticated users to bypass intended access restrictions and list the root directory via an FTP session.

Impact

Affected versions

pyftpdlib (<= 0.5.1)

Security releases

pyftpdlib → 0.5.2 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade pyftpdlib to 0.5.2 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2009-5012? CVE-2009-5012 is a high-severity security vulnerability in pyftpdlib (pip), affecting versions <= 0.5.1. It is fixed in 0.5.2.
  2. Which versions of pyftpdlib are affected by CVE-2009-5012? pyftpdlib (pip) versions <= 0.5.1 is affected.
  3. Is there a fix for CVE-2009-5012? Yes. CVE-2009-5012 is fixed in 0.5.2. Upgrade to this version or later.
  4. Is CVE-2009-5012 exploitable, and should I be worried? Whether CVE-2009-5012 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether CVE-2009-5012 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix CVE-2009-5012? Upgrade pyftpdlib to 0.5.2 or later.

Other vulnerabilities in pyftpdlib

Stop the waste.
Protect your environment with Kodem.