CVE-2022-36071 is a high-severity improper authentication vulnerability in github.com/drakkan/sftpgo/v2 (go), affecting versions >= 2.2.0, < 2.3.4. It is fixed in 2.3.4.
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
The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.
CVE-2022-36071 has a CVSS score of 8.3 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (2.3.4). Upgrading removes the vulnerable code path.
go
github.com/drakkan/sftpgo/v2 (>= 2.2.0, < 2.3.4)github.com/drakkan/sftpgo/v2 → 2.3.4 (go)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2022-36071 is reachable in your applications. Explore open-source security for your team.
See if CVE-2022-36071 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2022-36071 in your environment →Upgrade github.com/drakkan/sftpgo/v2 to 2.3.4 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2022-36071 is a high-severity improper authentication vulnerability in github.com/drakkan/sftpgo/v2 (go), affecting versions >= 2.2.0, < 2.3.4. It is fixed in 2.3.4. The application does not adequately verify the identity of a user, device, or process before granting access.
CVE-2022-36071 has a CVSS score of 8.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
github.com/drakkan/sftpgo/v2 (go) versions >= 2.2.0, < 2.3.4 is affected.
Yes. CVE-2022-36071 is fixed in 2.3.4. Upgrade to this version or later.
Whether CVE-2022-36071 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade github.com/drakkan/sftpgo/v2 to 2.3.4 or later.