Summary
SFTPGo allows administrators to restrict command execution from the EventManager
Workarounds
Allow EventManager to be used only by SFTPGo administrators who also have shell access.
Impact
One powerful feature of SFTPGo is the ability to have the EventManager execute scripts or run applications in response to certain events.
This feature is very common in all software similar to SFTPGo and is generally unrestricted.
However, any SFTPGo administrator with permission to run a script has access to the underlying OS/container with the same permissions as the user running SFTPGo, so they can access the database and server configurations.
This is unexpected for some SFTPGo administrators who think that there is a clear distinction between accessing the system shell and accessing the SFTPGo WebAdmin UI.
Affected versions
Security releases
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
To avoid this confusion, running system commands is now disabled by default, and an allow list has been added so that system administrators configuring SFTPGo must explicitly define which commands are allowed to be configured from the WebAdmin UI.
https://github.com/drakkan/sftpgo/commit/88b1850b5806eee81150873d4e565144b21021fb
https://github.com/drakkan/sftpgo/commit/b524da11e9466d05fe03304713ee1c61bb276ec4
Frequently Asked Questions
- What is CVE-2024-52309? CVE-2024-52309 is a medium-severity security vulnerability in github.com/drakkan/sftpgo/v2 (go), affecting versions >= 2.4.0, < 2.6.3. It is fixed in 2.6.3.
- Which packages are affected by CVE-2024-52309?
github.com/drakkan/sftpgo/v2(go) (versions >= 2.4.0, < 2.6.3)sftpgo(go) (versions >= 2.4.0, < 2.6.3)
- Is there a fix for CVE-2024-52309? Yes. CVE-2024-52309 is fixed in 2.6.3. Upgrade to this version or later.
- Is CVE-2024-52309 exploitable, and should I be worried? Whether CVE-2024-52309 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
- What actually determines whether CVE-2024-52309 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.
- How do I fix CVE-2024-52309?
- Upgrade
github.com/drakkan/sftpgo/v2to 2.6.3 or later - Upgrade
sftpgoto 2.6.3 or later
- Upgrade