Skip to content
Noroxi
CVE-2022-3602· NVD / CVE Program· CNA openssl

X.509 Email Address 4-byte 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 the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious email address to overflow four attacker-controlled bytes on the stack. This buffer overflow could result in a crash (causing a denial of service) or potentially remote code execution. Many platforms implement stack overflow protections which would mitigate against the risk of remote code execution. The risk may be further mitigated based on stack layout for any given platform/compiler. Pre-announcements of CVE-2022-3602 described this issue as CRITICAL. Further analysis based on some of the mitigating factors described above have led this to be downgraded to HIGH. Users are still encouraged to upgrade to a new version as soon as possible. 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).

HighCVSS 7.5 · v3.1—Proof of concept Fix available
Published
Nov 1, 2022
Updated
Jun 17, 2026
EPSS
90.8% · 100th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

57

Plan

Add it to your regular patch cycle.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
27 / 30 · 90.8%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
opensslopenssl
fedoraprojectfedora
netappclustered data ontap
nodejsnode.js

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

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

    • 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)affected

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: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
openSUSE:Tumbleweedpython-mitmproxybefore 11.1.2-1.111.1.2-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
SUSE:Linux Enterprise Module for Basesystem 15 SP4openssl-3before 3.0.1-150400.4.11.13.0.1-150400.4.11.1

+1

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 remKEV
    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
  • CVE-2016-2108The ASN.1 implementation in OpenSSL before 1.0.1o and 1.0.2 before 1.0.2c allows remote attackers to execute arbitrary code or cause a denia
    62This week
  • CVE-2016-6309statem/statem.c in OpenSSL 1.1.0a does not consider memory-block movement after a realloc call, which allows remote attackers to cause a den
    60This week
  • CVE-2022-3786X.509 Email Address Variable Length Buffer Overflow
    58Plan

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
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)
opensuse:python-mitmproxy11.1.2-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 ×8

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:5282022-10-28
Proof-of-concept repository on GitHubstars:1692022-10-30
Proof-of-concept repository on GitHubstars:132022-10-31
Proof-of-concept repository on GitHubstars:32022-11-01
Proof-of-concept repository on GitHubstars:12022-11-02
Proof-of-concept repository on GitHubstars:172022-11-02
Proof-of-concept repository on GitHubstars:42022-11-03
Proof-of-concept repository on GitHubstars:42022-11-07

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. First PoC-5 d
  2. Published
  3. TodayOct 9, 2026+1438 d
EPSS, last 120 days+1% in 7 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

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

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

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 →

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-787 · Out-of-bounds Write

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records