{"answers":{"affected":"4 open source packages ship an affected version, including github.com/drakkan/sftpgo/v2 and github.com/drakkan/sftpgo.","exploited":"There is no known exploitation of CVE-2024-52801 in the wild and no public exploit code.","fix":"Upgrade github.com/drakkan/sftpgo/v2 to 2.6.4 or later.","what":"CVE-2024-52801 is a medium-severity vulnerability in drakkan sftpgo, published on 29 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-52801 and fix it if it is affected.\n\nWhat it is: CVE-2024-52801 is a medium-severity vulnerability in drakkan sftpgo, published on 29 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-52801 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/drakkan/sftpgo/v2 (Go): affected from 2.3.0; fixed in 2.6.4\n- github.com/drakkan/sftpgo/v2 (Go): affected from 2.3.0; fixed in 2.6.4\n- github.com/drakkan/sftpgo/v2 (Go): affected from 2.3.0; fixed in 2.6.4\n- github.com/drakkan/sftpgo (Go): affected all versions; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-52801/ (Markdown: https://insights.sbomify.com/CVE-2024-52801/index.md)","id":"CVE-2024-52801","markdown":"https://insights.sbomify.com/CVE-2024-52801/index.md","name":"CVE-2024-52801","record":{"aliases":["GHSA-6943-qr24-82vx","GO-2024-3300"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"SFTPGo file transfer","requires_auth":"low_privilege","summary":"Attackers can brute force predictable OpenID Connect session cookies to access other users' data in SFTPGo.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"sftpgo is a full-featured and highly configurable event-driven file transfer solution. Server protocols: SFTP, HTTP/S, FTP/S, WebDAV. The OpenID Connect implementation 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. This issue was fixed in version v2.6.4, where cookies are opaque and cryptographically secure strings. All users are advised to upgrade. There are no known workarounds for this vulnerability.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Brute force takeover of OpenID Connect session cookies in sftpgo","id":"CVE-2024-52801","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"weak_cryptography","year":"2024"},"n_packages":4,"n_references":3,"next":{"headline":"RIOT-OS missing dhcpv6_opt_t minimum header length check","id":"CVE-2024-52802"},"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":[],"package":"github.com/drakkan/sftpgo","purl":"pkg:golang/github.com/drakkan/sftpgo","source":"GO-2024-3300"},{"ecosystem":"Go","fixed":["2.6.4"],"introduced":["2.3.0"],"last_affected":[],"package":"github.com/drakkan/sftpgo/v2","purl":null,"source":"GHSA-6943-qr24-82vx"},{"ecosystem":"Go","fixed":["2.6.4"],"introduced":["2.3.0"],"last_affected":[],"package":"github.com/drakkan/sftpgo/v2","purl":"pkg:golang/github.com/drakkan/sftpgo/v2","source":"GHSA-6943-qr24-82vx"},{"ecosystem":"Go","fixed":["2.6.4"],"introduced":["2.3.0"],"last_affected":[],"package":"github.com/drakkan/sftpgo/v2","purl":"pkg:golang/github.com/drakkan/sftpgo/v2","source":"GO-2024-3300"}],"prev":{"headline":"Potential XXE (XML External Entity Injection) vulnerability in veraPDF CLI","id":"CVE-2024-52800"},"products":["sftpgo"],"published":"2024-11-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-12-02","vendors":["drakkan"]},"summary":"Attackers can brute force predictable OpenID Connect session cookies to access other users' data in SFTPGo.","url":"https://insights.sbomify.com/CVE-2024-52801/"}