GHSA-54qx-8p8w-xhg8
Suggest an improvement- Source
- https://github.com/advisories/GHSA-54qx-8p8w-xhg8
- Import Source
- https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/09/GHSA-54qx-8p8w-xhg8/GHSA-54qx-8p8w-xhg8.json
- JSON Data
- https://api.osv.dev/v1/vulns/GHSA-54qx-8p8w-xhg8
- Aliases
- Related
- Published
- 2022-09-16T21:05:28Z
- Modified
- 2024-08-21T16:28:54.483117Z
- Severity
-
- 8.3 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L CVSS Calculator
- Summary
- SFTPGo vulnerable to recovery codes abuse
- Details
-
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
- Database specific
{ "nvd_published_at": "2022-09-02T18:15:00Z", "github_reviewed_at": "2022-09-16T21:05:28Z", "severity": "HIGH", "github_reviewed": true, "cwe_ids": [ "CWE-287", "CWE-916" ] }- References
Affected packages
Go / github.com/drakkan/sftpgo/v2
Package
- Name
- github.com/drakkan/sftpgo/v2
- View open source insights on deps.dev
- Purl
- pkg:golang/github.com/drakkan/sftpgo/v2