LiveActive security incident?Get immediate response
CVE Record

CVE-2020-1967: Segmentation fault in SSL_check_chain

Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due to a NULL pointer dereference as a result of incorrect handling of the "signature_algorithms_cert" TLS extension. The crash occurs if an invalid or unrecognised signature algorithm is received from the peer. This could be exploited by a malicious peer in a Denial of Service attack. OpenSSL version 1.1.1d, 1.1.1e, and 1.1.1f are affected by this issue. This issue did not affect OpenSSL versions prior to 1.1.1d. Fixed in OpenSSL 1.1.1g (Affected 1.1.1d-1.1.1f).

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2020-1967 is a denial-of-service flaw in OpenSSL 1.1.1d through 1.1.1f. A malicious TLS peer can trigger a crash in applications that call SSL_check_chain during or after a TLS 1.3 handshake. The supplied sources indicate availability risk, not data theft. Exposure is likely where servers or clients use OpenSSL 1.1.1d, 1.1.1e, or 1.1.1f and application code calls SSL_check_chain with TLS 1.3. Distribution packages and bundled third-party products may carry patched OpenSSL versions, so product-specific advisories should be checked. Treat this as a targeted availability risk. It is not described as remote code execution, but crashing TLS-facing services can disrupt customer access and internal integrations. Patch affected OpenSSL builds promptly, starting with externally reachable and business-critical systems. Mitigation focus: Upgrade OpenSSL to 1.1.1g or a vendor-patched package.; Apply operating system security updates from affected distributions.; Check third-party appliance and software advisories for bundled OpenSSL exposure..

Prepared

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.

cve · low confidence lookup

CVE-2020-1967 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
28Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
OpenSSLOpenSSLFixed in OpenSSL 1.1.1g (Affected 1.1.1d-1.1.1f)Listed
Weakness

CWE details

No CWE listed

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