gsd-2022-3786
Vulnerability from gsd
Modified
2023-12-13 01:19
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 a malicious certificate or for an application to continue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious email address in a certificate to overflow an arbitrary number of bytes containing the `.' character (decimal 46) on the stack. This buffer overflow could result in a crash (causing a denial of service). 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.
Aliases
Aliases



{
  "GSD": {
    "alias": "CVE-2022-3786",
    "id": "GSD-2022-3786",
    "references": [
      "https://access.redhat.com/errata/RHSA-2022:7288",
      "https://access.redhat.com/errata/RHSA-2022:7384",
      "https://www.suse.com/security/cve/CVE-2022-3786.html"
    ]
  },
  "gsd": {
    "database_specific": {
      "GSD": {
        "affected_component": "X.509 Email Address handling",
        "aliases": [
          "CVE-2022-3786"
        ],
        "attack_vector": "network",
        "credit": "",
        "description": "X.509 Email Address Variable Length Buffer Overflow. CVE-2022-3786 was NOT rated as CRITICAL from the outset, because only the length and not the content of the overwrite is attacker controlled. Exposure to remote code execution is not expected on any platforms.",
        "impact": "unknown",
        "notes": "X.509 Email Address Variable Length Buffer Overflow.",
        "product_name": "openssl",
        "product_version": "3.0.5",
        "references": [
          "https://mta.openssl.org/pipermail/openssl-announce/2022-October/000238.html",
          "https://github.com/NCSC-NL/OpenSSL-2022",
          "https://www.bsi.bund.de/SharedDocs/Cybersicherheitswarnungen/DE/2022/2022-267005-1032.html",
          "https://github.com/pblumo/openssl-vuln-nov-2022/",
          "https://www.openssl.org/blog/blog/2022/11/01/email-address-overflows/",
          "https://github.com/openssl/openssl/commit/680e65b94c916af259bfdc2e25f1ab6e0c7a97d6",
          "https://www.openssl.org/source/openssl-3.0.7.tar.gz",
          "https://www.techsolvency.com/story-so-far/cve-tbd-openssl-3.0.7-critical/",
          "https://docs.google.com/spreadsheets/d/e/2PACX-1vT7ih8XJ5LHq-30saNCS9S7pJafe37S1b6ZRxWXcnx6HbrHFFTNIk7-gFQ7_NJlET47w0naS8deLtIG/pubhtml",
          "https://words.filippo.io/dispatches/openssl-punycode/"
        ],
        "vendor_name": "openssl",
        "vulnerability_type": "unknown"
      },
      "OSV": {
        "affected": [
          {
            "package": {
              "ecosystem": "GSD",
              "name": "openssl"
            },
            "versions": [
              "3.0.6",
              "3.0.5",
              "3.0.4",
              "3.0.3",
              "3.0.2",
              "3.0.1",
              "3.0.0",
              "3.0.0-beta2",
              "3.0.0-beta1",
              "3.0.0-alpha17",
              "3.0.0-alpha16",
              "3.0.0-alpha15",
              "3.0.0-alpha14",
              "3.0.0-alpha13",
              "3.0.0-alpha12",
              "3.0.0-alpha11",
              "3.0.0-alpha10",
              "3.0.0-alpha9",
              "3.0.0-alpha8",
              "3.0.0-alpha7",
              "3.0.0-alpha6",
              "3.0.0-alpha5",
              "3.0.0-alpha4",
              "3.0.0-alpha3",
              "3.0.0-alpha2",
              "3.0.0-alpha1"
            ]
          }
        ],
        "aliases": [
          "CVE-2022-3786"
        ],
        "details": "X.509 Email Address Variable Length Buffer Overflow. CVE-2022-3786 was NOT rated as CRITICAL from the outset, because only the length and not the content of the overwrite is attacker controlled. Exposure to remote code execution is not expected on any platforms.",
        "id": "CVE-2022-3786",
        "modified": "2022-11-02T15:48:10.308Z",
        "published": "2022-11-01T16:29:39.763Z",
        "references": [
          {
            "type": "WEB",
            "url": "https://mta.openssl.org/pipermail/openssl-announce/2022-October/000238.html"
          },
          {
            "type": "WEB",
            "url": "https://github.com/NCSC-NL/OpenSSL-2022"
          },
          {
            "type": "WEB",
            "url": "https://www.bsi.bund.de/SharedDocs/Cybersicherheitswarnungen/DE/2022/2022-267005-1032.html"
          },
          {
            "type": "WEB",
            "url": "https://github.com/pblumo/openssl-vuln-nov-2022/"
          },
          {
            "type": "ADVISORY",
            "url": "https://www.openssl.org/blog/blog/2022/11/01/email-address-overflows/"
          },
          {
            "type": "FIX",
            "url": "https://github.com/openssl/openssl/commit/680e65b94c916af259bfdc2e25f1ab6e0c7a97d6"
          },
          {
            "type": "FIX",
            "url": "https://www.openssl.org/source/openssl-3.0.7.tar.gz"
          },
          {
            "type": "WEB",
            "url": "https://www.techsolvency.com/story-so-far/cve-tbd-openssl-3.0.7-critical/"
          },
          {
            "type": "WEB",
            "url": "https://docs.google.com/spreadsheets/d/e/2PACX-1vT7ih8XJ5LHq-30saNCS9S7pJafe37S1b6ZRxWXcnx6HbrHFFTNIk7-gFQ7_NJlET47w0naS8deLtIG/pubhtml"
          },
          {
            "type": "WEB",
            "url": "https://words.filippo.io/dispatches/openssl-punycode/"
          }
        ],
        "summary": "X.509 Email Address Variable Length Buffer Overflow."
      }
    },
    "id": "GSD-2022-3786",
    "metadata": {
      "exploitCode": "unknown",
      "remediation": "unknown",
      "reportConfidence": "confirmed",
      "type": "vulnerability"
    },
    "modified": "2022-11-01T16:54:00.550547Z",
    "osvSchema": {
      "aliases": [
        "CVE-2022-3786"
      ],
      "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 a malicious certificate or for an application to continue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious email address in a certificate to overflow an arbitrary number of bytes containing the `.\u0027 character (decimal 46) on the stack. This buffer overflow could result in a crash (causing a denial of service). 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.",
      "id": "GSD-2022-3786",
      "modified": "2023-12-13T01:19:39.834654Z",
      "schema_version": "1.4.0"
    },
    "references": [
      {
        "type": "ADVISORY",
        "url": "https://mta.openssl.org/pipermail/openssl-announce/2022-October/000238.html"
      },
      {
        "type": "ADVISORY",
        "url": "https://github.com/NCSC-NL/OpenSSL-2022"
      },
      {
        "type": "ADVISORY",
        "url": "https://www.bsi.bund.de/SharedDocs/Cybersicherheitswarnungen/DE/2022/2022-267005-1032.html"
      },
      {
        "type": "ADVISORY",
        "url": "https://github.com/pblumo/openssl-vuln-nov-2022/"
      },
      {
        "type": "ADVISORY",
        "url": "https://www.openssl.org/blog/blog/2022/11/01/email-address-overflows/"
      },
      {
        "type": "FIX",
        "url": "https://github.com/openssl/openssl/commit/680e65b94c916af259bfdc2e25f1ab6e0c7a97d6"
      },
      {
        "type": "FIX",
        "url": "https://www.openssl.org/source/openssl-3.0.7.tar.gz"
      },
      {
        "type": "WEB",
        "url": "https://www.techsolvency.com/story-so-far/cve-tbd-openssl-3.0.7-critical/"
      },
      {
        "type": "WEB",
        "url": "https://docs.google.com/spreadsheets/d/e/2PACX-1vT7ih8XJ5LHq-30saNCS9S7pJafe37S1b6ZRxWXcnx6HbrHFFTNIk7-gFQ7_NJlET47w0naS8deLtIG/pubhtml"
      },
      {
        "type": "WEB",
        "url": "https://words.filippo.io/dispatches/openssl-punycode/"
      }
    ],
    "schema_version": "1.3.1"
  },
  "namespaces": {
    "cve.org": {
      "CVE_data_meta": {
        "ASSIGNER": "openssl-security@openssl.org",
        "ID": "CVE-2022-3786",
        "STATE": "PUBLIC"
      },
      "affects": {
        "vendor": {
          "vendor_data": [
            {
              "product": {
                "product_data": [
                  {
                    "product_name": "OpenSSL",
                    "version": {
                      "version_data": [
                        {
                          "version_affected": "=",
                          "version_value": "3.0.0"
                        }
                      ]
                    }
                  }
                ]
              },
              "vendor_name": "OpenSSL"
            }
          ]
        }
      },
      "credits": [
        {
          "lang": "en",
          "value": "Viktor Dukhovni"
        }
      ],
      "data_format": "MITRE",
      "data_type": "CVE",
      "data_version": "4.0",
      "description": {
        "description_data": [
          {
            "lang": "eng",
            "value": "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 a malicious certificate or for an application to continue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious email address in a certificate to overflow an arbitrary number of bytes containing the `.\u0027 character (decimal 46) on the stack. This buffer overflow could result in a crash (causing a denial of service). 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."
          }
        ]
      },
      "generator": {
        "engine": "Vulnogram 0.1.0-dev",
        "importer": "vulnxml2json5.py 2022-11-04 07:19:07.034873"
      },
      "problemtype": {
        "problemtype_data": [
          {
            "description": [
              {
                "lang": "eng",
                "value": "Buffer overflow"
              }
            ]
          }
        ]
      },
      "references": {
        "reference_data": [
          {
            "name": "https://www.openssl.org/news/secadv/20221101.txt",
            "refsource": "MISC",
            "url": "https://www.openssl.org/news/secadv/20221101.txt"
          },
          {
            "name": "https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=c42165b5706e42f67ef8ef4c351a9a4c5d21639a",
            "refsource": "MISC",
            "url": "https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=c42165b5706e42f67ef8ef4c351a9a4c5d21639a"
          }
        ]
      },
      "source": {
        "discovery": "UNKNOWN"
      }
    },
    "gitlab.com": {
      "advisories": [
        {
          "affected_range": "\u003e=3.0.0 \u003c3.0.7",
          "affected_versions": "All versions starting from 3.0.0 before 3.0.7",
          "cvss_v3": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
          "cwe_ids": [
            "CWE-1035",
            "CWE-120",
            "CWE-937"
          ],
          "date": "2023-01-19",
          "description": "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 a malicious certificate or for an application to continue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious email address in a certificate to overflow an arbitrary number of bytes containing the `.\u0027 character (decimal 46) on the stack. This buffer overflow could result in a crash (causing a denial of service). 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. Fixed in OpenSSL 3.0.7 (Affected 3.0.0,3.0.1,3.0.2,3.0.3,3.0.4,3.0.5,3.0.6).",
          "fixed_versions": [
            "3.0.7"
          ],
          "identifier": "CVE-2022-3786",
          "identifiers": [
            "CVE-2022-3786"
          ],
          "not_impacted": "All versions before 3.0.0, all versions starting from 3.0.7",
          "package_slug": "conan/openssl",
          "pubdate": "2022-11-01",
          "solution": "Upgrade to version 3.0.7 or above.",
          "title": "X.509 Email Address Variable Length Buffer Overflow",
          "urls": [
            "https://nvd.nist.gov/vuln/detail/CVE-2022-3786",
            "https://www.openssl.org/blog/blog/2022/11/01/email-address-overflows/",
            "https://www.openssl.org/news/secadv/20221101.txt"
          ],
          "uuid": "08e59ba6-c580-404e-a0e2-792f7334dc9a"
        }
      ]
    },
    "nvd.nist.gov": {
      "configurations": {
        "CVE_data_version": "4.0",
        "nodes": [
          {
            "children": [],
            "cpe_match": [
              {
                "cpe23Uri": "cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*",
                "cpe_name": [],
                "versionEndExcluding": "3.0.7",
                "versionStartIncluding": "3.0.0",
                "vulnerable": true
              }
            ],
            "operator": "OR"
          },
          {
            "children": [],
            "cpe_match": [
              {
                "cpe23Uri": "cpe:2.3:o:fedoraproject:fedora:36:*:*:*:*:*:*:*",
                "cpe_name": [],
                "vulnerable": true
              },
              {
                "cpe23Uri": "cpe:2.3:o:fedoraproject:fedora:37:*:*:*:*:*:*:*",
                "cpe_name": [],
                "vulnerable": true
              }
            ],
            "operator": "OR"
          },
          {
            "children": [],
            "cpe_match": [
              {
                "cpe23Uri": "cpe:2.3:a:nodejs:node.js:19.0.0:*:*:*:-:*:*:*",
                "cpe_name": [],
                "vulnerable": true
              },
              {
                "cpe23Uri": "cpe:2.3:a:nodejs:node.js:18.12.0:*:*:*:lts:*:*:*",
                "cpe_name": [],
                "vulnerable": true
              },
              {
                "cpe23Uri": "cpe:2.3:a:nodejs:node.js:*:*:*:*:-:*:*:*",
                "cpe_name": [],
                "versionEndExcluding": "18.11.0",
                "versionStartIncluding": "18.0.0",
                "vulnerable": true
              }
            ],
            "operator": "OR"
          }
        ]
      },
      "cve": {
        "CVE_data_meta": {
          "ASSIGNER": "openssl-security@openssl.org",
          "ID": "CVE-2022-3786"
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "en",
              "value": "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 a malicious certificate or for an application to continue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious email address in a certificate to overflow an arbitrary number of bytes containing the `.\u0027 character (decimal 46) on the stack. This buffer overflow could result in a crash (causing a denial of service). 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."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "en",
                  "value": "CWE-120"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://www.openssl.org/news/secadv/20221101.txt",
              "refsource": "CONFIRM",
              "tags": [
                "Vendor Advisory"
              ],
              "url": "https://www.openssl.org/news/secadv/20221101.txt"
            },
            {
              "name": "https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=c42165b5706e42f67ef8ef4c351a9a4c5d21639a",
              "refsource": "MISC",
              "tags": [
                "Patch",
                "Vendor Advisory"
              ],
              "url": "https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=c42165b5706e42f67ef8ef4c351a9a4c5d21639a"
            }
          ]
        }
      },
      "impact": {
        "baseMetricV3": {
          "cvssV3": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "HIGH",
            "baseScore": 7.5,
            "baseSeverity": "HIGH",
            "confidentialityImpact": "NONE",
            "integrityImpact": "NONE",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
            "version": "3.1"
          },
          "exploitabilityScore": 3.9,
          "impactScore": 3.6
        }
      },
      "lastModifiedDate": "2023-01-19T15:47Z",
      "publishedDate": "2022-11-01T18:15Z"
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading...

Loading...

Loading...
  • 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.