CVE-2022-3786
X.509 Email Address Variable Length Buffer Overflow
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 `.' 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.
Official description from the CVE record, published by openssl. Copyright © 1999-2026 The MITRE Corporation. See /security/cve/legal for the CVE license. View the record on cve.org
Key data
CVSS 3.1 High 7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Attack vector: Network
The vulnerable component can be reached over a network, possibly from the Internet.
Attack complexity: Low
No special conditions are needed. The attack can be repeated at will.
Privileges required: None
No account or privileges are needed.
User interaction: None
No action from any user is needed.
Scope: Unchanged
The impact stays within the vulnerable component.
Confidentiality impact: None
No effect on the secrecy of data.
Integrity impact: None
No effect on the trustworthiness of data.
Availability impact: High
Serious or total effect on availability.
| Metric | Value | What it means |
|---|---|---|
| Attack vector | Network | The vulnerable component can be reached over a network, possibly from the Internet. |
| Attack complexity | Low | No special conditions are needed. The attack can be repeated at will. |
| Privileges required | None | No account or privileges are needed. |
| User interaction | None | No action from any user is needed. |
| Scope | Unchanged | The impact stays within the vulnerable component. |
| Confidentiality impact | None | No effect on the secrecy of data. |
| Integrity impact | None | No effect on the trustworthiness of data. |
| Availability impact | High | Serious or total effect on availability. |
CVSS is owned and managed by FIRST.Org, Inc. (FIRST) and is used by permission. Each CVSS score on this site is shown together with its vector string, as published in the CVE record by the source named next to it. Learn more at first.org/cvss.
EPSS
- Score
- 0.92488 (92.5% probability)
- Percentile
- 99.8%
- Scores of
- Nov 10, 2026
- Model
- v2026.06.15
CISA assessment as of Apr 23, 2025
- Automatable
- yes
- Technical impact
- partial
Weakness (CWE)
- CWE-120Buffer Copy without Checking Size of Input
Affected products
OpenSSL
- affected: 3.0.0 up to before 3.0.7
References
- OpenSSL Advisory (openssl.org)vendor-advisory
- 3.0.7 git commit (git.openssl.org)patch
- intel.com/content/www/us/en/security-center/advisory/intel-…
- kb.cert.org/vuls/id/794340
Timeline
- ID reserved
- Record published
- Record last updated
Look up another CVE
About CubePath
Data from the CVE Program (MITRE), CISA KEV and FIRST EPSS. CVSS is owned by FIRST and used by permission. Not affiliated with or endorsed by MITRE, CISA or FIRST. Data as of Nov 10, 2026, 19:49 UTC. Sources and licenses