gsd-2021-36367
Vulnerability from gsd
Modified
2023-12-13 01:23
Details
PuTTY through 0.75 proceeds with establishing an SSH session even if it has never sent a substantive authentication response. This makes it easier for an attacker-controlled SSH server to present a later spoofed authentication prompt (that the attacker can use to capture credential data, and use that data for purposes that are undesired by the client user).
Aliases
Aliases



{
   GSD: {
      alias: "CVE-2021-36367",
      description: "PuTTY through 0.75 proceeds with establishing an SSH session even if it has never sent a substantive authentication response. This makes it easier for an attacker-controlled SSH server to present a later spoofed authentication prompt (that the attacker can use to capture credential data, and use that data for purposes that are undesired by the client user).",
      id: "GSD-2021-36367",
      references: [
         "https://security.archlinux.org/CVE-2021-36367",
      ],
   },
   gsd: {
      metadata: {
         exploitCode: "unknown",
         remediation: "unknown",
         reportConfidence: "confirmed",
         type: "vulnerability",
      },
      osvSchema: {
         aliases: [
            "CVE-2021-36367",
         ],
         details: "PuTTY through 0.75 proceeds with establishing an SSH session even if it has never sent a substantive authentication response. This makes it easier for an attacker-controlled SSH server to present a later spoofed authentication prompt (that the attacker can use to capture credential data, and use that data for purposes that are undesired by the client user).",
         id: "GSD-2021-36367",
         modified: "2023-12-13T01:23:16.948192Z",
         schema_version: "1.4.0",
      },
   },
   namespaces: {
      "cve.org": {
         CVE_data_meta: {
            ASSIGNER: "cve@mitre.org",
            ID: "CVE-2021-36367",
            STATE: "PUBLIC",
         },
         affects: {
            vendor: {
               vendor_data: [
                  {
                     product: {
                        product_data: [
                           {
                              product_name: "n/a",
                              version: {
                                 version_data: [
                                    {
                                       version_value: "n/a",
                                    },
                                 ],
                              },
                           },
                        ],
                     },
                     vendor_name: "n/a",
                  },
               ],
            },
         },
         data_format: "MITRE",
         data_type: "CVE",
         data_version: "4.0",
         description: {
            description_data: [
               {
                  lang: "eng",
                  value: "PuTTY through 0.75 proceeds with establishing an SSH session even if it has never sent a substantive authentication response. This makes it easier for an attacker-controlled SSH server to present a later spoofed authentication prompt (that the attacker can use to capture credential data, and use that data for purposes that are undesired by the client user).",
               },
            ],
         },
         problemtype: {
            problemtype_data: [
               {
                  description: [
                     {
                        lang: "eng",
                        value: "n/a",
                     },
                  ],
               },
            ],
         },
         references: {
            reference_data: [
               {
                  name: "https://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html",
                  refsource: "MISC",
                  url: "https://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html",
               },
               {
                  name: "https://git.tartarus.org/?p=simon/putty.git;a=commit;h=1dc5659aa62848f0aeb5de7bd3839fecc7debefa",
                  refsource: "MISC",
                  url: "https://git.tartarus.org/?p=simon/putty.git;a=commit;h=1dc5659aa62848f0aeb5de7bd3839fecc7debefa",
               },
               {
                  name: "DSA-5588",
                  refsource: "DEBIAN",
                  url: "https://www.debian.org/security/2023/dsa-5588",
               },
               {
                  name: "[debian-lts-announce] 20240425 [SECURITY] [DLA 3794-1] putty security update",
                  refsource: "MLIST",
                  url: "https://lists.debian.org/debian-lts-announce/2024/04/msg00016.html",
               },
            ],
         },
      },
      "nvd.nist.gov": {
         cve: {
            configurations: [
               {
                  nodes: [
                     {
                        cpeMatch: [
                           {
                              criteria: "cpe:2.3:a:putty:putty:*:*:*:*:*:*:*:*",
                              matchCriteriaId: "1159EB89-B30E-4381-8879-B40F5C935B62",
                              versionEndIncluding: "0.75",
                              vulnerable: true,
                           },
                        ],
                        negate: false,
                        operator: "OR",
                     },
                  ],
               },
            ],
            descriptions: [
               {
                  lang: "en",
                  value: "PuTTY through 0.75 proceeds with establishing an SSH session even if it has never sent a substantive authentication response. This makes it easier for an attacker-controlled SSH server to present a later spoofed authentication prompt (that the attacker can use to capture credential data, and use that data for purposes that are undesired by the client user).",
               },
               {
                  lang: "es",
                  value: "PuTTY versiones hasta 0.75, procede con establecer una sesión SSH incluso si nunca ha enviado una respuesta de autenticación sustantiva. Esto facilita a un servidor SSH controlado por un atacante presentar una petición de autenticación falsa posterior (que el atacante puede usar para capturar los datos de las credenciales, y usar esos datos para fines no deseados por el usuario cliente)",
               },
            ],
            id: "CVE-2021-36367",
            lastModified: "2024-04-25T22:15:07.883",
            metrics: {
               cvssMetricV2: [
                  {
                     acInsufInfo: false,
                     baseSeverity: "MEDIUM",
                     cvssData: {
                        accessComplexity: "MEDIUM",
                        accessVector: "NETWORK",
                        authentication: "NONE",
                        availabilityImpact: "NONE",
                        baseScore: 5.8,
                        confidentialityImpact: "PARTIAL",
                        integrityImpact: "PARTIAL",
                        vectorString: "AV:N/AC:M/Au:N/C:P/I:P/A:N",
                        version: "2.0",
                     },
                     exploitabilityScore: 8.6,
                     impactScore: 4.9,
                     obtainAllPrivilege: false,
                     obtainOtherPrivilege: false,
                     obtainUserPrivilege: false,
                     source: "nvd@nist.gov",
                     type: "Primary",
                     userInteractionRequired: true,
                  },
               ],
               cvssMetricV31: [
                  {
                     cvssData: {
                        attackComplexity: "LOW",
                        attackVector: "NETWORK",
                        availabilityImpact: "NONE",
                        baseScore: 8.1,
                        baseSeverity: "HIGH",
                        confidentialityImpact: "HIGH",
                        integrityImpact: "HIGH",
                        privilegesRequired: "NONE",
                        scope: "UNCHANGED",
                        userInteraction: "REQUIRED",
                        vectorString: "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N",
                        version: "3.1",
                     },
                     exploitabilityScore: 2.8,
                     impactScore: 5.2,
                     source: "nvd@nist.gov",
                     type: "Primary",
                  },
               ],
            },
            published: "2021-07-09T21:15:08.540",
            references: [
               {
                  source: "cve@mitre.org",
                  url: "https://git.tartarus.org/?p=simon/putty.git%3Ba=commit%3Bh=1dc5659aa62848f0aeb5de7bd3839fecc7debefa",
               },
               {
                  source: "cve@mitre.org",
                  url: "https://lists.debian.org/debian-lts-announce/2024/04/msg00016.html",
               },
               {
                  source: "cve@mitre.org",
                  tags: [
                     "Release Notes",
                     "Third Party Advisory",
                  ],
                  url: "https://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html",
               },
               {
                  source: "cve@mitre.org",
                  url: "https://www.debian.org/security/2023/dsa-5588",
               },
            ],
            sourceIdentifier: "cve@mitre.org",
            vulnStatus: "Modified",
            weaknesses: [
               {
                  description: [
                     {
                        lang: "en",
                        value: "CWE-345",
                     },
                  ],
                  source: "nvd@nist.gov",
                  type: "Primary",
               },
            ],
         },
      },
   },
}


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.


Loading…

Loading…

Loading…

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.