cbcvebase.
CVE-2022-3602
published 2022-11-01

CVE-2022-3602: A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain…

PriorityP267high7.5CVSS 3.1
AVNACLPRNUINSUCNINAH
EPSS
89.80%
99.8th percentile
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).

Affected

26 ranges· showing 25
VendorProductVersion rangeFixed in
debianopenssl< openssl 3.0.7-1 (bookworm)openssl 3.0.7-1 (bookworm)
fedoraprojectfedora
fedoraprojectfedora
fedoraprojectfedora
fedoraprojectfedora
msrcazure_sdk_for_c
msrcmicrosoft_azure_kubernetes_service
msrcvcpkg
nodejsnode.js
nodejsnode.js
nodejsnode.js>= 18.0.0 < 18.11.018.11.0
opensslopenssl
opensslopenssl>= 0 < 3.0.7-13.0.7-1
opensslopenssl>= 0 < 3.0.7-13.0.7-1
opensslopenssl>= 0 < 3.0.7-13.0.7-1
opensslopenssl>= 0 < 3.0.2-0ubuntu1.73.0.2-0ubuntu1.7
opensslopenssl>= 3.0.0 < 3.0.73.0.7
paloaltocortex_data
paloaltocortex_xdr
paloaltocortex_xpanse
paloaltocortex_xsoar
paloaltoglobalprotect
paloaltopan-os
paloaltoprisma_access
paloaltoprisma_cloud

Detection & IOCsextracted from sources · hover to see the quote

  • Detect vulnerable OpenSSL versions (3.0.0 through 3.0.6) using the openssl version command on Linux hosts
  • Detect vulnerable OpenSSL on Amazon Linux using rpm or repoquery
  • Detect vulnerable OpenSSL on Debian/Ubuntu using dpkg-query
  • Detect vulnerable OpenSSL on RHEL/Fedora/Oracle/CentOS using rpm
  • Scan Docker images for vulnerable OpenSSL using docker scan plugin
  • Scan container images for vulnerable OpenSSL using Trivy SPDX output
  • The vulnerability is triggered via a maliciously crafted email address in an X.509 certificate's name constraint field; focus TLS inspection on certificate Subject Alternative Name (SAN) email fields for punycode-encoded values
  • The flaw is located in the punycode decoder component within OpenSSL libcrypto; monitor for crashes or anomalous behaviour in processes linked against libcrypto when processing TLS certificates
  • For TLS servers, exploitation requires mTLS (client authentication) to be enabled; audit server configurations for client certificate request settings as a prioritisation signal
  • Proof-of-concept exploits that crash OpenSSL (DoS) are publicly available; monitor for unexpected OpenSSL process crashes in TLS-terminating services
  • ·Only OpenSSL versions 3.0.0 through 3.0.6 are affected; OpenSSL 1.x is NOT impacted
  • ·Exploitation requires either a CA to have signed the malicious certificate, or the application to continue certificate verification despite path-building failure — unauthenticated exploitation is not possible
  • ·Many platforms implement stack overflow protections that mitigate RCE; the primary realistic impact is denial of service (crash)
  • ·As of the sources' writing, no working RCE exploits existed — only PoCs causing crashes; RCE exploitation requires specific per-target exploit development

CVSS provenance

nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
ghsa7.5HIGH
osv7.5HIGH
vendor_cisco7.5HIGH
vendor_debian7.5HIGH
vendor_msrc7.5HIGH
vendor_oracle7.5HIGH
vendor_redhat7.5HIGH
vendor_ubuntu7.5HIGH
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.