Advisory

GHSA-54qx-8p8w-xhg8

Also known as: CVE-2022-36071, GO-2022-0964

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

Severity

High Basis: The source's own band: HIGH

Dates

Published
2022-09-16 21:05 UTC
Modified
2024-08-21 16:28 UTC

Affected packages and fixes

github.com/drakkan/sftpgo/v2

Go · All systems

Affected

  • introduced 2.2.0, fixed 2.3.4 (semver)

Fixed versions

2.3.4

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences