Summary
sftpgo vulnerable to brute force takeover of OpenID Connect session cookies
References
https://github.com/drakkan/sftpgo/commit/f30a9a2095bf90c0661b04fe038e3b7efc788bc6
Impact
The OpenID Connect implementation, in the affected SFTPGo versions, allows authenticated users to brute force session cookies and thereby gain access to other users' data, since the cookies are generated predictably using the xid library and are therefore unique but not cryptographically secure.
The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES. Typical impact: compromised confidentiality or integrity of protected data.
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
This issue was fixed in version v2.6.4, where cookies are opaque and cryptographically secure strings.
Frequently Asked Questions
- What is CVE-2024-52801? CVE-2024-52801 is a medium-severity use of a broken or risky cryptographic algorithm vulnerability in github.com/drakkan/sftpgo/v2 (go), affecting versions >= 2.3.0, < 2.6.4. It is fixed in 2.6.4. The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES.
- Which versions of github.com/drakkan/sftpgo/v2 are affected by CVE-2024-52801? github.com/drakkan/sftpgo/v2 (go) versions >= 2.3.0, < 2.6.4 is affected.
- Is there a fix for CVE-2024-52801? Yes. CVE-2024-52801 is fixed in 2.6.4. Upgrade to this version or later.
- Is CVE-2024-52801 exploitable, and should I be worried? Whether CVE-2024-52801 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-52801 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-52801? Upgrade
github.com/drakkan/sftpgo/v2to 2.6.4 or later.