X.509 Email Address Variable Length Buffer Overflow
cve-program · CVE-2022-3786
PublishedA 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.
Read the publisher's advisoryeuvd · EUVD-2022-7358
PublishedA 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.
Read the publisher's advisorynvd · CVE-2022-3786
PublishedA 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.
Read the publisher's advisoryosv · GHSA-h8jm-2x53-xhp5
PublishedA 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.
Read the publisher's advisoryosv · RUSTSEC-2022-0065
PublishedA 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.
Read the publisher's advisoryAffected versions, risk and source history
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2022-3786
PublishedX.509 Email Address Variable Length Buffer Overflow
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.
- Source published
- 1 Nov 2022 00:00:00 UTC
- Source modified
- 14 Apr 2026 08:58:03 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
euvd · EUVD-2022-7358
PublishedA 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 certific…
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.
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Nov 1, 2022, 12:00:00 AM
dateUpdated: Apr 14, 2026, 8:58:03 AM
23 related source bulletins · separate from aliases
WID-SEC-W-2023-0561: Xerox FreeFlow Print Server: Mehrere Schwachstellen
CVE-2023-21900 · CVE-2023-21843 · CVE-2023-21835 · CVE-2023-21830 · CVE-2022-46882 · CVE-2022-46881 · CVE-2022-46880 · CVE-2022-46878 · CVE-2022-46875 · CVE-2022-46874 · CVE-2022-46872 · CVE-2022-45421 · CVE-2022-45420 · CVE-2022-45419 · CVE-2022-45418 · CVE-2022-45417 · CVE-2022-45416 · CVE-2022-45415 · CVE-2022-45414 · CVE-2022-45413 · CVE-2022-45412 · CVE-2022-45411 · CVE-2022-45410 · CVE-2022-45409 · CVE-2022-45408 · CVE-2022-45407 · CVE-2022-45406 · CVE-2022-45405 · CVE-2022-45404 · CVE-2022-45403 · CVE-2022-45063 · CVE-2022-45061 · CVE-2022-44638 · CVE-2022-43680 · CVE-2022-43548 · CVE-2022-42932 · CVE-2022-42929 · CVE-2022-42928 · CVE-2022-42927 · CVE-2022-42252 · CVE-2022-41556 · CVE-2022-41323 · CVE-2022-40962 · CVE-2022-40960 · CVE-2022-40959 · CVE-2022-40958 · CVE-2022-40957 · CVE-2022-40956 · CVE-2022-40674 · CVE-2022-3970 · CVE-2022-39260 · CVE-2022-39253 · CVE-2022-3786 · CVE-2022-37797 · CVE-2022-37454 · CVE-2022-37436 · CVE-2022-36760 · CVE-2022-3627 · CVE-2022-3626 · CVE-2022-36087 · CVE-2022-36059 · CVE-2022-3602 · CVE-2022-3599 · CVE-2022-3598 · CVE-2022-3597 · CVE-2022-3570 · CVE-2022-35256 · CVE-2022-35255 · CVE-2022-34526 · CVE-2022-3276 · CVE-2022-32222 · CVE-2022-32215 · CVE-2022-32213 · CVE-2022-32212 · CVE-2022-3204 · CVE-2022-3190 · CVE-2022-31630 · CVE-2022-31629 · CVE-2022-31628 · CVE-2022-3155 · CVE-2022-3034 · CVE-2022-3033 · CVE-2022-3032 · CVE-2022-29458 · CVE-2022-29187 · CVE-2022-29154 · CVE-2022-2869 · CVE-2022-2868 · CVE-2022-2867 · CVE-2022-27406 · CVE-2022-27405 · CVE-2022-27404 · CVE-2022-26981 · CVE-2022-24765 · CVE-2022-24070 · CVE-2022-23901 · CVE-2022-22844 · CVE-2022-2210 · CVE-2022-2208 · CVE-2022-2207 · CVE-2022-2206 · CVE-2022-2183 · CVE-2022-2175 · CVE-2022-21658 · CVE-2022-21628 · CVE-2022-21626 · CVE-2022-21624 · CVE-2022-21619 · CVE-2022-2125 · CVE-2022-2122 · CVE-2022-2058 · CVE-2022-2057 · CVE-2022-2056 · CVE-2022-1925 · CVE-2022-1924 · CVE-2022-1923 · CVE-2022-1922 · CVE-2022-1921 · CVE-2022-1920 · CVE-2022-1348 · CVE-2022-1056 · CVE-2022-0924 · CVE-2022-0909 · CVE-2022-0908 · CVE-2022-0907 · CVE-2022-0891 · CVE-2022-0865 · CVE-2022-0562 · CVE-2022-0561 · CVE-2021-46848 · CVE-2021-46823 · CVE-2021-42694 · CVE-2021-42574 · CVE-2021-37750 · CVE-2021-28544 · CVE-2020-10735 · CVE-2019-6111 · CVE-2018-7160 · CVE-2015-20107 · CVE-2006-20001
ICSA-22-349-09: Siemens Products affected by OpenSSL 3.0
CVE-2022-3602 · CVE-2022-3786
openSUSE-SU-2024:12469-1: cargo-audit-advisory-db-20221102-1.1 on GA media
CVE-2022-3602 · CVE-2022-36086 · CVE-2022-3786
ICSA-23-019-01: Hitachi Energy PCU400
CVE-2022-3602 · CVE-2022-3786
ICSA-22-349-12: Siemens Parasolid
CVE-2022-3602 · CVE-2022-3786
openSUSE-SU-2025:14740-1: python311-cryptography-vectors-44.0.0-1.1 on GA media
CVE-2022-3602 · CVE-2022-3786
ICSA-23-005-03: Hitachi Energy Lumada Asset Performance Management
CVE-2022-3602 · CVE-2022-3786 · CVE-2022-37434
NCSC-2025-0123: Kwetsbaarheden verholpen in Oracle Database Producten
CVE-2020-1935 · CVE-2020-1938 · CVE-2020-9484 · CVE-2020-11996 · CVE-2020-13935 · CVE-2020-13943 · CVE-2020-36843 · CVE-2021-24122 · CVE-2021-25122 · CVE-2021-25329 · CVE-2021-30640 · CVE-2021-33037 · CVE-2021-41079 · CVE-2021-41184 · CVE-2021-42575 · CVE-2021-43980 · CVE-2022-3786 · CVE-2022-25762 · CVE-2022-42252 · CVE-2023-28708 · CVE-2023-34053 · CVE-2023-41080 · CVE-2023-42795 · CVE-2023-44487 · CVE-2023-45648 · CVE-2023-46589 · CVE-2024-6763 · CVE-2024-8176 · CVE-2024-8184 · CVE-2024-9143 · CVE-2024-11053 · CVE-2024-11233 · CVE-2024-11234 · CVE-2024-11236 · CVE-2024-13176 · CVE-2024-23672 · CVE-2024-24549 · CVE-2024-36114 · CVE-2024-37891 · CVE-2024-38819 · CVE-2024-38820 · CVE-2024-38999 · CVE-2024-39338 · CVE-2024-47554 · CVE-2024-47561 · CVE-2024-53382 · CVE-2024-57699 · CVE-2025-21578 · CVE-2025-24813 · CVE-2025-24970 · CVE-2025-25193 · CVE-2025-26791 · CVE-2025-30694 · CVE-2025-30701 · CVE-2025-30702 · CVE-2025-30733 · CVE-2025-30736
ICSA-22-349-11: Siemens SIPROTEC 5 Devices
CVE-2022-45044
openSUSE-SU-2024:12475-1: libopenssl-3-devel-3.0.7-1.1 on GA media
CVE-2022-3358 · CVE-2022-3602 · CVE-2022-3786
RHSA-2022:7384: Red Hat Security Advisory: openssl-container security update
CVE-2022-3602 · CVE-2022-3786
ICSA-22-349-10: Siemens APOGEE/TALON Field Panels
CVE-2022-3602 · CVE-2022-3786
openSUSE-SU-2025:14739-1: python311-cryptography-44.0.0-1.1 on GA media
CVE-2022-3602 · CVE-2022-3786 · CVE-2023-23931
ICSA-23-229-01: ICONICS and Mitsubishi Electric Products
CVE-2022-3602 · CVE-2022-3786 · CVE-2022-4203 · CVE-2022-4304 · CVE-2022-4450 · CVE-2023-0401
SSA-408105: SSA-408105: Buffer Overflow Vulnerabilities in OpenSSL 3.0 Affecting Siemens Products
CVE-2022-3602 · CVE-2022-3786
RHSA-2022:7288: Red Hat Security Advisory: openssl security update
CVE-2022-3602 · CVE-2022-3786
WID-SEC-W-2023-1969: HPE Fabric OS: Mehrere Schwachstellen ermöglichen Privilegieneskalation
CVE-2023-31928 · CVE-2023-31927 · CVE-2023-31926 · CVE-2023-31432 · CVE-2023-31431 · CVE-2023-31430 · CVE-2023-31429 · CVE-2023-31428 · CVE-2023-31427 · CVE-2023-31426 · CVE-2023-31425 · CVE-2022-44792 · CVE-2022-3786 · CVE-2022-3602 · CVE-2022-29154 · CVE-2022-28615 · CVE-2022-28614 · CVE-2022-25313 · CVE-2022-25236 · CVE-2022-25235 · CVE-2022-24448 · CVE-2022-23219 · CVE-2022-2097 · CVE-2022-2068 · CVE-2022-0778 · CVE-2022-0322 · CVE-2022-0155 · CVE-2021-45486 · CVE-2021-45485 · CVE-2021-41617 · CVE-2021-4145 · CVE-2021-39275 · CVE-2021-3800 · CVE-2021-20193 · CVE-2021-0146 · CVE-2020-36558 · CVE-2020-36557 · CVE-2020-15861 · CVE-2020-14145 · CVE-2019-0220 · CVE-2018-7738 · CVE-2018-25032 · CVE-2018-14404 · CVE-2018-14348 · CVE-2018-0739 · CVE-2014-2524 · CVE-2012-0060 · CVE-2011-4917
WID-SEC-W-2022-1922: OpenSSL: Mehrere Schwachstellen
CVE-2022-3602 · CVE-2022-3786
SUSE-SU-2022:3843-1: Security update for openssl-3
CVE-2022-3358 · CVE-2022-3602 · CVE-2022-3786
SUSE-SU-2022:4586-1: Security update for openssl-3
CVE-2022-3786 · CVE-2022-3996
openSUSE-SU-2024:12479-1: python310-cryptography-38.0.3-1.1 on GA media
CVE-2022-3602 · CVE-2022-3786
openSUSE-SU-2024:12480-1: python310-cryptography-vectors-38.0.3-1.1 on GA media
CVE-2022-3602 · CVE-2022-3786
cisco-sa-openssl-W9sdCc2a: Vulnerabilities in OpenSSL Affecting Cisco Products: November 2022
CVE-2022-3602 · CVE-2022-3786
- Source published
- Nov 1, 2022, 12:00:00 AM (timezone not stated)
- Source modified
- Apr 14, 2026, 8:58:03 AM (timezone not stated)
- Saved here
- 18 Nov 2026 03:31:12 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 3.1 · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd · CVE-2022-3786
PublishedA 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 certific…
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.
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Modified
Weakness classifications: CWE-120
Original publisher date fields
published: 2022-11-01T18:15:11.047
lastModified: 2026-06-17T05:00:18.193
6 source CPE criteria · context only
- cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*
- cpe:2.3:o:fedoraproject:fedora:36:*:*:*:*:*:*:*
- cpe:2.3:o:fedoraproject:fedora:37:*:*:*:*:*:*:*
- cpe:2.3:a:nodejs:node.js:*:*:*:*:-:*:*:*
- cpe:2.3:a:nodejs:node.js:18.12.0:*:*:*:lts:*:*:*
- cpe:2.3:a:nodejs:node.js:19.0.0:*:*:*:-:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
- Source published
- 1 Nov 2022 18:15:11 UTC
- Source modified
- 17 Jun 2026 05:00:18 UTC
- Saved here
- 24 Oct 2026 20:17:36 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · [email protected] · Primary · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 3.1 · 134c704f-9b21-4f2e-91b3-4a467353bcc0 · Secondary · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
osv · GHSA-h8jm-2x53-xhp5
PublishedX.509 Email Address Variable Length Buffer Overflow
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.
- Source published
- 1 Nov 2022 17:45:21 UTC
- Source modified
- 10 Sep 2026 03:49:49 UTC
- Saved here
- 24 Oct 2026 13:19:54 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Publisher rating · HIGH
osv · RUSTSEC-2022-0065
PublishedX.509 Email Address Variable Length Buffer Overflow
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.
- Source published
- 1 Nov 2022 12:00:00 UTC
- Source modified
- 16 Dec 2024 15:27:12 UTC
- Saved here
- 24 Oct 2026 13:19:54 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.