SFTPGo vulnerable to recovery codes abuse

CAO 8.1CVE-2022-36071 · GHSA-54qx-8p8w-xhg8 · GO-2022-0964 · Công bố 02/09/2022 · cập nhật 17/06/2026

Tóm tắt nhanh

CVE-2022-36071 là lỗ hổng mức CAO (CVSS 8.1) ảnh hưởng github.com/drakkan/sftpgo, github.com/drakkan/sftpgo/v2, sftpgo (sftpgo project).
Xác suất bị khai thác trong 30 ngày tới (EPSS): 0.55%, cao hơn 45.9% các lỗ hổng khác.
Cách xử lý: cập nhật lên 2.3.4 hoặc mới hơn.

Gói / sản phẩm	Phiên bản bị ảnh hưởng	Phiên bản đã vá
github.com/drakkan/sftpgo Go	`mọi phiên bản`	Chưa có bản vá
github.com/drakkan/sftpgo/v2 Go	`≥ 2.2.0, < 2.3.4`	`2.3.4`
sftpgo sftpgo_project	`≥ 2.2.0, < 2.3.4`	`2.3.4`

Mô tả

Impact

SFTPGo WebAdmin and WebClient support login using TOTP (Time-based One Time Passwords) as a seconday authentication factor. Because TOTPs are often configured on mobile devices that can be lost, stolen or damaged, SFTPGo also supports recovery codes. These are a set of one time use codes that can be used instead of the TOTP.

In SFTPGo versions from v2.2.0 to v2.3.3 recovery codes can be generated before enabling two-factor authentication. An attacker who knows the user's password could potentially generate some recovery codes and then bypass two-factor authentication after it is enabled on the account at a later time.

Patches

Fixed in v2.3.4. Recovery codes can now only be generated after enabling two-factor authentication and are deleted after disabling it.

Workarounds

Regenerate recovery codes after enabling two-factor authentication.

References

https://github.com/drakkan/sftpgo/issues/965

Mô tả của NVD

SFTPGo is configurable SFTP server with optional HTTP/S, FTP/S and WebDAV support. SFTPGo WebAdmin and WebClient support login using TOTP (Time-based One Time Passwords) as a secondary authentication factor. Because TOTPs are often configured on mobile devices that can be lost, stolen or damaged, SFTPGo also supports recovery codes. These are a set of one time use codes that can be used instead of the TOTP. In SFTPGo versions from version 2.2.0 to 2.3.3 recovery codes can be generated before enabling two-factor authentication. An attacker who knows the user's password could potentially generate some recovery codes and then bypass two-factor authentication after it is enabled on the account at a later time. This issue has been fixed in version 2.3.4. Recovery codes can now only be generated after enabling two-factor authentication and are deleted after disabling it.