ghsa-8rwr-x37p-mx23
Vulnerability from github
Published
2022-11-01 17:45
Modified
2022-11-07 21:28
Severity ?
Summary
X.509 Email Address 4-byte Buffer Overflow
Details

A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious email address to overflow four attacker-controlled bytes on the stack. This buffer overflow could result in a crash (causing a denial of service) or potentially remote code execution.

Many platforms implement stack overflow protections which would mitigate against the risk of remote code execution. The risk may be further mitigated based on stack layout for any given platform/compiler.

Pre-announcements of CVE-2022-3602 described this issue as CRITICAL. Further analysis based on some of the mitigating factors described above have led this to be downgraded to HIGH. Users are still encouraged to upgrade to a new version as soon as possible.

In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects.

Show details on source website


{
   affected: [
      {
         package: {
            ecosystem: "crates.io",
            name: "openssl-src",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "300.0.0",
                  },
                  {
                     fixed: "300.0.11",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2022-3602",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-120",
         "CWE-787",
      ],
      github_reviewed: true,
      github_reviewed_at: "2022-11-01T17:45:59Z",
      nvd_published_at: "2022-11-01T18:15:00Z",
      severity: "CRITICAL",
   },
   details: "A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs\nafter certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to\ncontinue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious email address\nto overflow four attacker-controlled bytes on the stack. This buffer overflow could result in a crash (causing a denial of service) or\npotentially remote code execution.\n\nMany platforms implement stack overflow protections which would mitigate against the risk of remote code execution. The risk may be further mitigated based on stack layout for any given platform/compiler.\n\nPre-announcements of CVE-2022-3602 described this issue as CRITICAL. Further analysis based on some of the mitigating factors described above have led this to be downgraded to HIGH. Users are still encouraged to upgrade to a new version as soon as possible.\n\nIn a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects.\n",
   id: "GHSA-8rwr-x37p-mx23",
   modified: "2022-11-07T21:28:54Z",
   published: "2022-11-01T17:45:59Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2022-3602",
      },
      {
         type: "WEB",
         url: "https://github.com/rustsec/advisory-db/pull/1452",
      },
      {
         type: "WEB",
         url: "https://github.com/alexcrichton/openssl-src-rs/commit/4a31c14f31e1a08c18893a37e304dd1dd4b7daa3",
      },
      {
         type: "WEB",
         url: "https://github.com/openssl/openssl/commit/fe3b639dc19b325846f4f6801f2f4604f56e3de3",
      },
      {
         type: "WEB",
         url: "https://www.openssl.org/news/secadv/20221101.txt",
      },
      {
         type: "WEB",
         url: "https://www.kb.cert.org/vuls/id/794340",
      },
      {
         type: "WEB",
         url: "https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-openssl-W9sdCc2a",
      },
      {
         type: "WEB",
         url: "https://security.netapp.com/advisory/ntap-20221102-0001",
      },
      {
         type: "WEB",
         url: "https://security.gentoo.org/glsa/202211-01",
      },
      {
         type: "WEB",
         url: "https://rustsec.org/advisories/RUSTSEC-2022-0064.html",
      },
      {
         type: "WEB",
         url: "https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2022-0023",
      },
      {
         type: "WEB",
         url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DWP23EZYOBDJQP7HP4YU7W2ABU2YDITS",
      },
      {
         type: "WEB",
         url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/63YRPWPUSX3MBHNPIEJZDKQT6YA7UF6S",
      },
      {
         type: "WEB",
         url: "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/DWP23EZYOBDJQP7HP4YU7W2ABU2YDITS",
      },
      {
         type: "WEB",
         url: "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/63YRPWPUSX3MBHNPIEJZDKQT6YA7UF6S",
      },
      {
         type: "PACKAGE",
         url: "https://github.com/alexcrichton/openssl-src-rs",
      },
      {
         type: "WEB",
         url: "https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=fe3b639dc19b325846f4f6801f2f4604f56e3de3",
      },
      {
         type: "WEB",
         url: "https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=fe3b639dc19b325846f4f6801f2f4604f56e3de3",
      },
      {
         type: "WEB",
         url: "http://packetstormsecurity.com/files/169687/OpenSSL-Security-Advisory-20221101.html",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/01/15",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/01/16",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/01/17",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/01/18",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/01/19",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/01/20",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/01/21",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/01/24",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/02/1",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/02/10",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/02/11",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/02/12",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/02/13",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/02/14",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/02/15",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/02/2",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/02/3",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/02/5",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/02/6",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/02/7",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/02/9",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/03/1",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/03/10",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/03/11",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/03/2",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/03/3",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/03/5",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/03/6",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/03/7",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2022/11/03/9",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
         type: "CVSS_V3",
      },
   ],
   summary: "X.509 Email Address 4-byte Buffer Overflow",
}


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.