CVE-2022-36071 (GCVE-0-2022-36071)
Vulnerability from cvelistv5
Published
2022-09-02 17:15
Modified
2024-08-03 09:52
Severity ?
8.3 (High) - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
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.
References
security-advisories@github.comhttps://github.com/drakkan/sftpgo/issues/965Exploit, Issue Tracking, Patch, Third Party Advisory
security-advisories@github.comhttps://github.com/drakkan/sftpgo/security/advisories/GHSA-54qx-8p8w-xhg8Mitigation, Third Party Advisory
af854a3a-2127-422b-91ae-364da2661108https://github.com/drakkan/sftpgo/issues/965Exploit, Issue Tracking, Patch, Third Party Advisory
af854a3a-2127-422b-91ae-364da2661108https://github.com/drakkan/sftpgo/security/advisories/GHSA-54qx-8p8w-xhg8Mitigation, Third Party Advisory
Impacted products
Vendor Product Version
drakkan sftpgo Version: >= 2.2.0, < 2.3.4
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
   containers: {
      adp: [
         {
            providerMetadata: {
               dateUpdated: "2024-08-03T09:52:00.281Z",
               orgId: "af854a3a-2127-422b-91ae-364da2661108",
               shortName: "CVE",
            },
            references: [
               {
                  tags: [
                     "x_refsource_CONFIRM",
                     "x_transferred",
                  ],
                  url: "https://github.com/drakkan/sftpgo/security/advisories/GHSA-54qx-8p8w-xhg8",
               },
               {
                  tags: [
                     "x_refsource_MISC",
                     "x_transferred",
                  ],
                  url: "https://github.com/drakkan/sftpgo/issues/965",
               },
            ],
            title: "CVE Program Container",
         },
      ],
      cna: {
         affected: [
            {
               product: "sftpgo",
               vendor: "drakkan",
               versions: [
                  {
                     status: "affected",
                     version: ">= 2.2.0, < 2.3.4",
                  },
               ],
            },
         ],
         descriptions: [
            {
               lang: "en",
               value: "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.",
            },
         ],
         metrics: [
            {
               cvssV3_1: {
                  attackComplexity: "LOW",
                  attackVector: "NETWORK",
                  availabilityImpact: "LOW",
                  baseScore: 8.3,
                  baseSeverity: "HIGH",
                  confidentialityImpact: "HIGH",
                  integrityImpact: "HIGH",
                  privilegesRequired: "LOW",
                  scope: "UNCHANGED",
                  userInteraction: "NONE",
                  vectorString: "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L",
                  version: "3.1",
               },
            },
         ],
         problemTypes: [
            {
               descriptions: [
                  {
                     cweId: "CWE-287",
                     description: "CWE-287: Improper Authentication",
                     lang: "en",
                     type: "CWE",
                  },
               ],
            },
         ],
         providerMetadata: {
            dateUpdated: "2022-09-02T17:15:12",
            orgId: "a0819718-46f1-4df5-94e2-005712e83aaa",
            shortName: "GitHub_M",
         },
         references: [
            {
               tags: [
                  "x_refsource_CONFIRM",
               ],
               url: "https://github.com/drakkan/sftpgo/security/advisories/GHSA-54qx-8p8w-xhg8",
            },
            {
               tags: [
                  "x_refsource_MISC",
               ],
               url: "https://github.com/drakkan/sftpgo/issues/965",
            },
         ],
         source: {
            advisory: "GHSA-54qx-8p8w-xhg8",
            discovery: "UNKNOWN",
         },
         title: "Recovery codes abuse in SFTPGo",
         x_legacyV4Record: {
            CVE_data_meta: {
               ASSIGNER: "security-advisories@github.com",
               ID: "CVE-2022-36071",
               STATE: "PUBLIC",
               TITLE: "Recovery codes abuse in SFTPGo",
            },
            affects: {
               vendor: {
                  vendor_data: [
                     {
                        product: {
                           product_data: [
                              {
                                 product_name: "sftpgo",
                                 version: {
                                    version_data: [
                                       {
                                          version_value: ">= 2.2.0, < 2.3.4",
                                       },
                                    ],
                                 },
                              },
                           ],
                        },
                        vendor_name: "drakkan",
                     },
                  ],
               },
            },
            data_format: "MITRE",
            data_type: "CVE",
            data_version: "4.0",
            description: {
               description_data: [
                  {
                     lang: "eng",
                     value: "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.",
                  },
               ],
            },
            impact: {
               cvss: {
                  attackComplexity: "LOW",
                  attackVector: "NETWORK",
                  availabilityImpact: "LOW",
                  baseScore: 8.3,
                  baseSeverity: "HIGH",
                  confidentialityImpact: "HIGH",
                  integrityImpact: "HIGH",
                  privilegesRequired: "LOW",
                  scope: "UNCHANGED",
                  userInteraction: "NONE",
                  vectorString: "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L",
                  version: "3.1",
               },
            },
            problemtype: {
               problemtype_data: [
                  {
                     description: [
                        {
                           lang: "eng",
                           value: "CWE-287: Improper Authentication",
                        },
                     ],
                  },
               ],
            },
            references: {
               reference_data: [
                  {
                     name: "https://github.com/drakkan/sftpgo/security/advisories/GHSA-54qx-8p8w-xhg8",
                     refsource: "CONFIRM",
                     url: "https://github.com/drakkan/sftpgo/security/advisories/GHSA-54qx-8p8w-xhg8",
                  },
                  {
                     name: "https://github.com/drakkan/sftpgo/issues/965",
                     refsource: "MISC",
                     url: "https://github.com/drakkan/sftpgo/issues/965",
                  },
               ],
            },
            source: {
               advisory: "GHSA-54qx-8p8w-xhg8",
               discovery: "UNKNOWN",
            },
         },
      },
   },
   cveMetadata: {
      assignerOrgId: "a0819718-46f1-4df5-94e2-005712e83aaa",
      assignerShortName: "GitHub_M",
      cveId: "CVE-2022-36071",
      datePublished: "2022-09-02T17:15:12",
      dateReserved: "2022-07-15T00:00:00",
      dateUpdated: "2024-08-03T09:52:00.281Z",
      state: "PUBLISHED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.1",
   "vulnerability-lookup:meta": {
      fkie_nvd: {
         configurations: "[{\"nodes\": [{\"operator\": \"OR\", \"negate\": false, \"cpeMatch\": [{\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:sftpgo_project:sftpgo:*:*:*:*:*:*:*:*\", \"versionStartIncluding\": \"2.2.0\", \"versionEndExcluding\": \"2.3.4\", \"matchCriteriaId\": \"154C23FB-9676-4167-A174-476FB50A6C06\"}]}]}]",
         descriptions: "[{\"lang\": \"en\", \"value\": \"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.\"}, {\"lang\": \"es\", \"value\": \"SFTPGo es un servidor SFTP configurable con soporte opcional HTTP/S, FTP/S y WebDAV. SFTPGo WebAdmin y WebClient admiten el inicio de sesi\\u00f3n mediante TOTP (Time-based One Time Passwords) como factor de autenticaci\\u00f3n secundario. Debido a que los TOTPs son configurados a menudo en dispositivos m\\u00f3viles que pueden ser perdidos, robados o da\\u00f1ados, SFTPGo tambi\\u00e9n soporta c\\u00f3digos de recuperaci\\u00f3n. Estos son un conjunto de c\\u00f3digos de un solo uso que pueden ser usados en lugar de la TOTP. En las versiones de SFTPGo desde la versi\\u00f3n 2.2.0 hasta 2.3.3, los c\\u00f3digos de recuperaci\\u00f3n pueden generarse antes de habilitar la autenticaci\\u00f3n de dos factores. Un atacante que conozca la contrase\\u00f1a del usuario podr\\u00eda generar potencialmente algunos c\\u00f3digos de recuperaci\\u00f3n y luego omitir la autenticaci\\u00f3n de dos factores despu\\u00e9s de habilitarla en la cuenta en un momento posterior. Este problema ha sido corregido en versi\\u00f3n 2.3.4. Los c\\u00f3digos de recuperaci\\u00f3n ahora s\\u00f3lo pueden generarse despu\\u00e9s de habilitar la autenticaci\\u00f3n de dos factores y sean eliminados despu\\u00e9s de deshabilitarla\"}]",
         id: "CVE-2022-36071",
         lastModified: "2024-11-21T07:12:19.060",
         metrics: "{\"cvssMetricV31\": [{\"source\": \"security-advisories@github.com\", \"type\": \"Secondary\", \"cvssData\": {\"version\": \"3.1\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L\", \"baseScore\": 8.3, \"baseSeverity\": \"HIGH\", \"attackVector\": \"NETWORK\", \"attackComplexity\": \"LOW\", \"privilegesRequired\": \"LOW\", \"userInteraction\": \"NONE\", \"scope\": \"UNCHANGED\", \"confidentialityImpact\": \"HIGH\", \"integrityImpact\": \"HIGH\", \"availabilityImpact\": \"LOW\"}, \"exploitabilityScore\": 2.8, \"impactScore\": 5.5}, {\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"cvssData\": {\"version\": \"3.1\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N\", \"baseScore\": 8.1, \"baseSeverity\": \"HIGH\", \"attackVector\": \"NETWORK\", \"attackComplexity\": \"LOW\", \"privilegesRequired\": \"LOW\", \"userInteraction\": \"NONE\", \"scope\": \"UNCHANGED\", \"confidentialityImpact\": \"HIGH\", \"integrityImpact\": \"HIGH\", \"availabilityImpact\": \"NONE\"}, \"exploitabilityScore\": 2.8, \"impactScore\": 5.2}]}",
         published: "2022-09-02T18:15:12.150",
         references: "[{\"url\": \"https://github.com/drakkan/sftpgo/issues/965\", \"source\": \"security-advisories@github.com\", \"tags\": [\"Exploit\", \"Issue Tracking\", \"Patch\", \"Third Party Advisory\"]}, {\"url\": \"https://github.com/drakkan/sftpgo/security/advisories/GHSA-54qx-8p8w-xhg8\", \"source\": \"security-advisories@github.com\", \"tags\": [\"Mitigation\", \"Third Party Advisory\"]}, {\"url\": \"https://github.com/drakkan/sftpgo/issues/965\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\", \"tags\": [\"Exploit\", \"Issue Tracking\", \"Patch\", \"Third Party Advisory\"]}, {\"url\": \"https://github.com/drakkan/sftpgo/security/advisories/GHSA-54qx-8p8w-xhg8\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\", \"tags\": [\"Mitigation\", \"Third Party Advisory\"]}]",
         sourceIdentifier: "security-advisories@github.com",
         vulnStatus: "Modified",
         weaknesses: "[{\"source\": \"security-advisories@github.com\", \"type\": \"Secondary\", \"description\": [{\"lang\": \"en\", \"value\": \"CWE-287\"}]}, {\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"description\": [{\"lang\": \"en\", \"value\": \"CWE-916\"}]}]",
      },
      nvd: "{\"cve\":{\"id\":\"CVE-2022-36071\",\"sourceIdentifier\":\"security-advisories@github.com\",\"published\":\"2022-09-02T18:15:12.150\",\"lastModified\":\"2024-11-21T07:12:19.060\",\"vulnStatus\":\"Modified\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"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.\"},{\"lang\":\"es\",\"value\":\"SFTPGo es un servidor SFTP configurable con soporte opcional HTTP/S, FTP/S y WebDAV. SFTPGo WebAdmin y WebClient admiten el inicio de sesión mediante TOTP (Time-based One Time Passwords) como factor de autenticación secundario. Debido a que los TOTPs son configurados a menudo en dispositivos móviles que pueden ser perdidos, robados o dañados, SFTPGo también soporta códigos de recuperación. Estos son un conjunto de códigos de un solo uso que pueden ser usados en lugar de la TOTP. En las versiones de SFTPGo desde la versión 2.2.0 hasta 2.3.3, los códigos de recuperación pueden generarse antes de habilitar la autenticación de dos factores. Un atacante que conozca la contraseña del usuario podría generar potencialmente algunos códigos de recuperación y luego omitir la autenticación de dos factores después de habilitarla en la cuenta en un momento posterior. Este problema ha sido corregido en versión 2.3.4. Los códigos de recuperación ahora sólo pueden generarse después de habilitar la autenticación de dos factores y sean eliminados después de deshabilitarla\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L\",\"baseScore\":8.3,\"baseSeverity\":\"HIGH\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"LOW\"},\"exploitabilityScore\":2.8,\"impactScore\":5.5},{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N\",\"baseScore\":8.1,\"baseSeverity\":\"HIGH\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"NONE\"},\"exploitabilityScore\":2.8,\"impactScore\":5.2}]},\"weaknesses\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-287\"}]},{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-916\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:sftpgo_project:sftpgo:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"2.2.0\",\"versionEndExcluding\":\"2.3.4\",\"matchCriteriaId\":\"154C23FB-9676-4167-A174-476FB50A6C06\"}]}]}],\"references\":[{\"url\":\"https://github.com/drakkan/sftpgo/issues/965\",\"source\":\"security-advisories@github.com\",\"tags\":[\"Exploit\",\"Issue Tracking\",\"Patch\",\"Third Party Advisory\"]},{\"url\":\"https://github.com/drakkan/sftpgo/security/advisories/GHSA-54qx-8p8w-xhg8\",\"source\":\"security-advisories@github.com\",\"tags\":[\"Mitigation\",\"Third Party Advisory\"]},{\"url\":\"https://github.com/drakkan/sftpgo/issues/965\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Exploit\",\"Issue Tracking\",\"Patch\",\"Third Party Advisory\"]},{\"url\":\"https://github.com/drakkan/sftpgo/security/advisories/GHSA-54qx-8p8w-xhg8\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Mitigation\",\"Third Party Advisory\"]}]}}",
   },
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.