LiveActive security incident?Get immediate response
CVE Record

CVE-2022-3786: X.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.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-3786 is an OpenSSL certificate-validation flaw that can crash affected software during TLS certificate checks. It is most relevant where systems use affected OpenSSL 3.x code and process attacker-controlled certificates. The public evidence supports denial of service risk, not data theft or code execution.

Executive priority

Treat as a high-priority availability risk, especially for services whose outage would affect customers or operations. Patch according to vendor guidance, but avoid emergency assumptions about data compromise unless separate evidence exists.

Technical view

The flaw is a stack buffer overrun in X.509 name constraint checking for certificate email addresses. It occurs after chain signature verification and requires either a malicious CA-signed certificate or verification continuing after path-building failure. Reported impact is availability loss through crash.

Likely exposure

Exposure is likely where OpenSSL 3.0.0 is present in applications, appliances, or embedded products that perform X.509 verification. TLS clients can be affected by malicious servers; TLS servers are relevant when client certificate authentication is enabled.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. Attack feasibility depends on certificate-handling conditions, but the CVSS vector is network, low complexity, no privileges, no user interaction, with high availability impact.

Researcher notes

Important constraints are the name-constraint path, email address handling, and post-signature-verification timing. The sources describe crash-oriented impact. They do not establish active exploitation, broad product scope beyond referenced vendors, or a universal mitigation beyond applying vendor fixes.

Mitigation direction

  • Apply OpenSSL and downstream vendor updates tied to CVE-2022-3786.
  • Prioritize internet-facing TLS clients and servers using client certificate authentication.
  • Check Intel, CERT/CC, Siemens, and other supplier advisories for product-specific fixes.
  • Avoid continuing certificate verification after untrusted path construction failures.
  • Track remaining affected assets until vendor remediation is confirmed.

Validation and detection

  • Inventory OpenSSL versions in hosts, containers, appliances, and bundled applications.
  • Confirm whether applications use OpenSSL 3.0.0 for X.509 certificate verification.
  • Identify TLS servers that request or require client certificates.
  • Review vendor advisories for affected product versions and fixed releases.
  • Verify patched builds through package metadata, SBOMs, or vendor release evidence.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-120: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-3786 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2022-3786Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
OpenSSLOpenSSL3.0.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.