nday
CVE-2021-3450

CA certificate check bypass with X509_V_FLAG_X509_STRICT

OpenSSL / OpenSSL

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

cryptographic failure
CWE-295, stated by NVD's analysts
remote, unauthenticated
AV:N, PR:N, UI:N in CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N (CVSS 3.1) from NVD's analysts
network
AV:N in CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N (CVSS 3.1) from NVD's analysts
no authentication required
PR:N in CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N (CVSS 3.1) from NVD's analysts
no user interaction
UI:N in CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N (CVSS 3.1) from NVD's analysts
FreeBSD
CPE names NVD's analysts give as vulnerable: o:freebsd:freebsd
SonicOS
CPE names NVD's analysts give as vulnerable: o:sonicwall:sonicos
SonicWall SMA
CPE names NVD's analysts give as vulnerable: o:sonicwall:sma100_firmware
MySQL
CPE names NVD's analysts give as vulnerable: a:oracle:mysql_connectors, a:oracle:mysql_enterprise_monitor, a:oracle:mysql_server, a:oracle:mysql_workbench
WebLogic Server
CPE names NVD's analysts give as vulnerable: a:oracle:weblogic_server
Node.js
CPE names NVD's analysts give as vulnerable: a:nodejs:node.js
PeopleSoft
CPE names NVD's analysts give as vulnerable: a:oracle:peoplesoft_enterprise_peopletools
JD Edwards
CPE names NVD's analysts give as vulnerable: a:oracle:jd_edwards_enterpriseone_tools, a:oracle:jd_edwards_world_security
OpenSSL
affected products in the CVE record: OpenSSL · OpenSSLCPE names NVD's analysts give as vulnerable: a:openssl:openssl
operating system
CPE names NVD's analysts give as vulnerable: o:freebsd:freebsdthe product type of FreeBSD in nday's product registry
firewall / VPN / security gateway
CPE names NVD's analysts give as vulnerable: o:sonicwall:sma100_firmware, o:sonicwall:sonicosthe product type of SonicOS and SonicWall SMA in nday's product registry
database
CPE names NVD's analysts give as vulnerable: a:oracle:mysql_connectors, a:oracle:mysql_enterprise_monitor, a:oracle:mysql_server, a:oracle:mysql_workbenchthe product type of MySQL in nday's product registry
web / application server
CPE names NVD's analysts give as vulnerable: a:oracle:weblogic_serverthe product type of WebLogic Server in nday's product registry
enterprise application (ERP/CRM)
CPE names NVD's analysts give as vulnerable: a:oracle:jd_edwards_enterpriseone_tools, a:oracle:jd_edwards_world_security, a:oracle:peoplesoft_enterprise_peopletoolsthe product type of JD Edwards and PeopleSoft in nday's product registry
endpoint security / antivirus
CPE names NVD's analysts give as vulnerable: a:mcafee:web_gateway, a:mcafee:web_gateway_cloud_servicenday's type rule vendor:mcafee-trellix
open-source library / framework
affected products in the CVE record: OpenSSL · OpenSSLCPE names NVD's analysts give as vulnerable: a:nodejs:node.js, a:openssl:opensslthe product type of Node.js and OpenSSL in nday's product registry
stage
DIS
disclosed
cvss
no score yet

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2021-03-25T14:25Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a "purpose" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named "purpose" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j).

Original text of the CVE record (cvelist), shown as published.

Event log

+DISdisclosed

CVE record published by openssl.

src cvelist · nday , bulk import · raw
{
  "id": 233668,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2021-3450",
  "occurred_at": "2021-03-25T14:25:14.287Z",
  "observed_at": "2026-11-13T05:37:17.325681Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "ssvc": {
      "timestamp": "2026-10-08T21:02:24.642640Z",
      "automatable": "yes",
      "exploitation": "none",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2021-03-25T14:25:14.287Z",
    "assigner_short_name": "openssl"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.