Skip to content
Noroxi
NVD / CVE Program· CNA openssl

CVE-2022-3786: X.509 Email Address Variable Length Buffer Overflow

HighCVSS 7.5 · v3.1—Proof of concept Fix available

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

Report tools

JSON

Action score

58

Plan

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.

Follow CVE-2022-3786

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Check your server's TLS configurationRun the SSL check

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Check your server's TLS configurationRun the SSL check

Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
opensslopenssl
fedoraprojectfedora
nodejsnode.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 check

Versions 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.

EcosystemPackageAffected rangeFix
AlmaLinux:9opensslbefore 1:3.0.1-43.el9_01:3.0.1-43.el9_0
AlmaLinux:9openssl-develbefore 1:3.0.1-43.el9_01:3.0.1-43.el9_0
AlmaLinux:9openssl-libsbefore 1:3.0.1-43.el9_01:3.0.1-43.el9_0
AlmaLinux:9openssl-perlbefore 1:3.0.1-43.el9_01:3.0.1-43.el9_0
Alpine:v3.15openssl3before 3.0.7-r03.0.7-r0
Alpine:v3.17nodejsbefore 18.12.1-r018.12.1-r0
Alpine:v3.17opensslfrom 3.0.0 · before 3.0.7-r03.0.7-r0
crates.ioopenssl-srcfrom 300.0.0 · before 300.0.11300.0.11
Debian:12opensslbefore 3.0.7-13.0.7-1
openSUSE:Leap 15.4openssl-3before 3.0.1-150400.4.11.13.0.1-150400.4.11.1
openSUSE:Leap 15.4openssl-3before 3.0.1-150400.4.14.13.0.1-150400.4.14.1
openSUSE:Tumbleweedcargo-audit-advisory-dbbefore 20221102-1.120221102-1.1
openSUSE:Tumbleweedopenssl-3before 3.0.7-1.13.0.7-1.1
openSUSE:Tumbleweedpython-cryptographybefore 38.0.3-1.138.0.3-1.1
openSUSE:Tumbleweedpython-cryptographybefore 44.0.0-1.144.0.0-1.1
openSUSE:Tumbleweedpython-cryptography-vectorsbefore 44.0.0-1.144.0.0-1.1
Red Hat:enterprise_linux:9::appstreamopenssl-debuginfobefore 1:3.0.1-43.el9_01:3.0.1-43.el9_0
Red Hat:enterprise_linux:9::appstreamopenssl-debugsourcebefore 1:3.0.1-43.el9_01:3.0.1-43.el9_0
Red Hat:enterprise_linux:9::appstreamopenssl-develbefore 1:3.0.1-43.el9_01:3.0.1-43.el9_0
Red Hat:enterprise_linux:9::appstreamopenssl-libs-debuginfobefore 1:3.0.1-43.el9_01:3.0.1-43.el9_0
Red Hat:enterprise_linux:9::appstreamopenssl-perlbefore 1:3.0.1-43.el9_01:3.0.1-43.el9_0
Red Hat:enterprise_linux:9::baseosopensslbefore 1:3.0.1-43.el9_01:3.0.1-43.el9_0
Red Hat:enterprise_linux:9::baseosopenssl-libsbefore 1:3.0.1-43.el9_01:3.0.1-43.el9_0
Rocky Linux:9opensslbefore 1:3.0.1-43.el9_01:3.0.1-43.el9_0

+2

Other 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…KEV
    90Now
  • CVE-2021-3711SM2 Decryption Buffer Overflow
    65This 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 encryption
    60This week
  • ← EarlierCVE-2022-3602Nov 1, 2022 · X.509 Email Address 4-byte Buffer Overflow
    57Plan
  • Later →CVE-2022-3996Dec 13, 2022 · X.509 Policy Constraints Double Locking
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
OpenSSL OpenSSL3.0.7Vendor (CNA)
almalinux:openssl1:3.0.1-43.el9_0 · AlmaLinux:9Package registry (OSV)
almalinux:openssl-devel1:3.0.1-43.el9_0 · AlmaLinux:9Package registry (OSV)
almalinux:openssl-libs1:3.0.1-43.el9_0 · AlmaLinux:9Package registry (OSV)
almalinux:openssl-perl1:3.0.1-43.el9_0 · AlmaLinux:9Package registry (OSV)
alpine:nodejs18.12.1-r0 · Alpine:v3.17Package registry (OSV)
alpine:openssl3.0.7-r0 · Alpine:v3.17Package registry (OSV)
alpine:openssl33.0.7-r0 · Alpine:v3.15Package registry (OSV)
crates.io:openssl-src300.0.11Package registry (OSV)
debian:openssl3.0.7-1 · Debian:12Package registry (OSV)
opensuse:cargo-audit-advisory-db20221102-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:openssl-33.0.1-150400.4.11.1 · openSUSE:Leap 15.4Package registry (OSV)
opensuse:python-cryptography38.0.3-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:python-cryptography-vectors44.0.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:openssl1:3.0.1-43.el9_0 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:openssl-debuginfo1:3.0.1-43.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:openssl-debugsource1:3.0.1-43.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:openssl-devel1:3.0.1-43.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:openssl-libs1:3.0.1-43.el9_0 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:openssl-libs-debuginfo1:3.0.1-43.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:openssl-perl1:3.0.1-43.el9_0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
rocky linux:openssl1:3.0.1-43.el9_0 · Rocky Linux:9Package registry (OSV)
suse:openssl-33.0.1-150400.4.11.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP4Package 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.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:52023-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.

  1. Published
  2. First PoC+70 d
  3. 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.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

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.

All national notices →

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

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.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
char buf[256];memcpy(buf, pkt->data, pkt->len);

Fixed

c
char buf[256];if (pkt->len > sizeof(buf)) {  return -EINVAL;}memcpy(buf, pkt->data, pkt->len);

References

All records