CVE-2022-3786: X.509 Email Address Variable Length Buffer Overflow
Noroxi assessment
Priority: Plan (action score 58/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 92.4% (FIRST EPSS); higher than 99.8% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: OpenSSL OpenSSL 3.0.7.
- Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Add it to your regular patch cycle. Upgrade to OpenSSL OpenSSL 3.0.7 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Nov 1, 2022
- Updated
- Jun 17, 2026
- EPSS
- 92.4% · 99th percentile
- CWE
- CWE-120
Report tools
Action score
58
Add it to your regular patch cycle.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 28 / 30 · 92.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Check your server's TLS configurationRun the SSL check
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| openssl | openssl | cpe:2.3:a:openssl:openssl |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| nodejs | node.js | cpe:2.3:a:nodejs:node.js |
Check your server's TLS configuration
The OpenSSL version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.
Run the SSL checkVersions reported by the vendor
Affected version ranges reported by the assigning authority (openssl). Independent of NVD's CPE analysis and usually ahead of it.
OpenSSL OpenSSL
- 3.0.0 and later · before 3.0.7affected · semver
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- nodejs node.js18.0.0 and later · before 18.11.0
- nodejs node.js18.12.0
- nodejs node.js19.0.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:9 | openssl | before 1:3.0.1-43.el9_0 | 1:3.0.1-43.el9_0 |
| AlmaLinux:9 | openssl-devel | before 1:3.0.1-43.el9_0 | 1:3.0.1-43.el9_0 |
| AlmaLinux:9 | openssl-libs | before 1:3.0.1-43.el9_0 | 1:3.0.1-43.el9_0 |
| AlmaLinux:9 | openssl-perl | before 1:3.0.1-43.el9_0 | 1:3.0.1-43.el9_0 |
| Alpine:v3.15 | openssl3 | before 3.0.7-r0 | 3.0.7-r0 |
| Alpine:v3.17 | nodejs | before 18.12.1-r0 | 18.12.1-r0 |
| Alpine:v3.17 | openssl | from 3.0.0 · before 3.0.7-r0 | 3.0.7-r0 |
| crates.io | openssl-src | from 300.0.0 · before 300.0.11 | 300.0.11 |
| Debian:12 | openssl | before 3.0.7-1 | 3.0.7-1 |
| openSUSE:Leap 15.4 | openssl-3 | before 3.0.1-150400.4.11.1 | 3.0.1-150400.4.11.1 |
| openSUSE:Leap 15.4 | openssl-3 | before 3.0.1-150400.4.14.1 | 3.0.1-150400.4.14.1 |
| openSUSE:Tumbleweed | cargo-audit-advisory-db | before 20221102-1.1 | 20221102-1.1 |
| openSUSE:Tumbleweed | openssl-3 | before 3.0.7-1.1 | 3.0.7-1.1 |
| openSUSE:Tumbleweed | python-cryptography | before 38.0.3-1.1 | 38.0.3-1.1 |
| openSUSE:Tumbleweed | python-cryptography | before 44.0.0-1.1 | 44.0.0-1.1 |
| openSUSE:Tumbleweed | python-cryptography-vectors | before 44.0.0-1.1 | 44.0.0-1.1 |
| Red Hat:enterprise_linux:9::appstream | openssl-debuginfo | before 1:3.0.1-43.el9_0 | 1:3.0.1-43.el9_0 |
| Red Hat:enterprise_linux:9::appstream | openssl-debugsource | before 1:3.0.1-43.el9_0 | 1:3.0.1-43.el9_0 |
| Red Hat:enterprise_linux:9::appstream | openssl-devel | before 1:3.0.1-43.el9_0 | 1:3.0.1-43.el9_0 |
| Red Hat:enterprise_linux:9::appstream | openssl-libs-debuginfo | before 1:3.0.1-43.el9_0 | 1:3.0.1-43.el9_0 |
| Red Hat:enterprise_linux:9::appstream | openssl-perl | before 1:3.0.1-43.el9_0 | 1:3.0.1-43.el9_0 |
| Red Hat:enterprise_linux:9::baseos | openssl | before 1:3.0.1-43.el9_0 | 1:3.0.1-43.el9_0 |
| Red Hat:enterprise_linux:9::baseos | openssl-libs | before 1:3.0.1-43.el9_0 | 1:3.0.1-43.el9_0 |
| Rocky Linux:9 | openssl | before 1:3.0.1-43.el9_0 | 1:3.0.1-43.el9_0 |
+2
Same product
openssl: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows…KEV90Now
- CVE-2021-3711SM2 Decryption Buffer Overflow65This week
- CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code…65This week
Published before and after this one in the same product
- ← EarlierCVE-2022-3358Oct 11, 2022 · Using a Custom Cipher with NID_undef may lead to NULL encryption60This week
- ← EarlierCVE-2022-3602Nov 1, 2022 · X.509 Email Address 4-byte Buffer Overflow57Plan
- Later →CVE-2022-3996Dec 13, 2022 · X.509 Policy Constraints Double Locking30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| OpenSSL OpenSSL | 3.0.7 | Vendor (CNA) |
| almalinux:openssl | 1:3.0.1-43.el9_0 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:openssl-devel | 1:3.0.1-43.el9_0 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:openssl-libs | 1:3.0.1-43.el9_0 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:openssl-perl | 1:3.0.1-43.el9_0 · AlmaLinux:9 | Package registry (OSV) |
| alpine:nodejs | 18.12.1-r0 · Alpine:v3.17 | Package registry (OSV) |
| alpine:openssl | 3.0.7-r0 · Alpine:v3.17 | Package registry (OSV) |
| alpine:openssl3 | 3.0.7-r0 · Alpine:v3.15 | Package registry (OSV) |
| crates.io:openssl-src | 300.0.11 | Package registry (OSV) |
| debian:openssl | 3.0.7-1 · Debian:12 | Package registry (OSV) |
| opensuse:cargo-audit-advisory-db | 20221102-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:openssl-3 | 3.0.1-150400.4.11.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:python-cryptography | 38.0.3-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:python-cryptography-vectors | 44.0.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:openssl | 1:3.0.1-43.el9_0 · Red Hat:enterprise_linux:9::baseos | Package registry (OSV) |
| red hat:openssl-debuginfo | 1:3.0.1-43.el9_0 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:openssl-debugsource | 1:3.0.1-43.el9_0 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:openssl-devel | 1:3.0.1-43.el9_0 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:openssl-libs | 1:3.0.1-43.el9_0 · Red Hat:enterprise_linux:9::baseos | Package registry (OSV) |
| red hat:openssl-libs-debuginfo | 1:3.0.1-43.el9_0 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:openssl-perl | 1:3.0.1-43.el9_0 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| rocky linux:openssl | 1:3.0.1-43.el9_0 · Rocky Linux:9 | Package registry (OSV) |
| suse:openssl-3 | 3.0.1-150400.4.11.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP4 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:5 | 2023-01-11 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+70 d
- TodayNov 17, 2026+1477 d
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Viktor Dukhovnifinder
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-22-0729 · Dec 12, 2022(OpenSSL Güvenlik Güncellemesi )
- TR-22-0682 · Nov 9, 2022(Microsoft Güvenlik Güncellemesi)
Not on record for this CVE: EPSS history · variant or chain candidate.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Root cause
When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.
The bug in code
The whole CWE-120 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
char buf[256];
memcpy(buf, pkt->data, pkt->len);Fixed
char buf[256];
if (pkt->len > sizeof(buf)) {
return -EINVAL;
}
memcpy(buf, pkt->data, pkt->len);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
- Overflow Variables and TagsCAPEC-46likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.