Chaindrakkan · sftpgoGo:github.com/drakkan/sftpgo/v2
drakkan sftpgo: successive fixes (2024)
3 CVEs over 2 generations, 20 Jun 2024 to 29 Nov 2024.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2024-3789720 Jun 2024 First in the chain
- CVE-2024-5230921 Nov 2024 related to CVE-2024-37897
- CVE-2024-5280129 Nov 2024 related to CVE-2024-37897next fix after CVE-2024-52309
Exploited in the wild (CISA KEV) Not in KEV Priority score (0 to 100) High confidence Medium Low Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
CVEs in this family
Table view of the tree| CVE | Published | Title | Linked from | Priority |
|---|---|---|---|---|
| CVE-2024-37897 | 20 Jun 2024 | Insufficient access control for password reset in sftpgo · fixed in 2.6.1 | First in chain | 8.5 |
| CVE-2024-52309 | 21 Nov 2024 | SFTPGo allows administrators to restrict command execution from the EventManager · fixed in 2.6.3 | CVE-2024-37897 · related · High | 13.6 |
| CVE-2024-52801 | 29 Nov 2024 | Brute force takeover of OpenID Connect session cookies in sftpgo · fixed in 2.6.4 | CVE-2024-37897 · related · Medium | 10.7 |