CVE-2022-36071 json
Recovery codes abuse in SFTPGo
published 4y ago modified 4mo ago also GHSA-54qx-8p8w-xhg8 , GO-2022-0964 , EUVD-2022-6703
- cvss
- 8.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 46%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/drakkan/sftpgo/v2 2.3.4
- sftpgo_project sftpgo 2.3.4
- github.com/drakkan/sftpgo/issues/965 advisory
Is CVE-2022-36071 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.55% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/drakkan/sftpgo/issues/965 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L |
| NVD | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
| GitHub | 3.1 | 8.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/drakkan/sftpgo/v2 | >=2.2.0, <2.3.4 |
2.3.4 |
| go | github.com/drakkan/sftpgo | all versions |
no fix listed |
Affected products
- drakkan sftpgo
Classification
References
-
github.com
/drakkan/sftpgo/issues/965
web, exploit, issue-tracking, patch, third-party-advisory, report
-
github.com
/drakkan/sftpgo/security/advisories/GHSA-54qx-8p8w-xhg8
web, mitigation, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-36071
advisory
-
github.com
/drakkan/sftpgo
package
Sources
- CVE List CVE-2022-36071
- GitHub Advisory GHSA-54qx-8p8w-xhg8
- NVD CVE-2022-36071
- OSV GO-2022-0964
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.