Skip to content
Fencer Intel
high 7.5

CVE-2020-1967 in the critical feed json

Segmentation fault in SSL_check_chain

published 6y ago modified last mo. also EUVD-2021-1780 , GHSA-jq65-29v4-4x35 , JLSEC-2026-219 , RUSTSEC-2020-0015

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
53.3%
EPSS 53.3% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known

Summary

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).

Patch / fix

  • crates.io openssl-src 111.9.0
  • julia OpenSSL_jll 1.1.10+0
  • jdedwards enterpriseone 9.2.5.0
  • tenable log_correlation_engine 6.0.9
  • openssl Debian 14, Debian 13, Debian 12 1.1.1g-1

debian advisories DEBIAN-CVE-2020-1967

  • openssl Ubuntu 20.04 LTS 1.1.1f-1ubuntu2

ubuntu advisories UBUNTU-CVE-2020-1967

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • rust SLE Module for Development Tools 15 SP2, SLE Module for Development Tools 15 SP1 1.43.1-12.1
  • openssl-1_1 SLES for SAP 12 SP5, SLES for SAP 12 SP4, SLES 12 SP5 +3 more 1.1.1d-2.23.1

suse advisories SUSE-SU-2020:2041-1SUSE-SU-2020:1058-1

  • openssl-1_1 openSUSE Tumbleweed 1.1.1l-1.2
  • rust1.53 openSUSE Tumbleweed 1.53.0-2.5
  • rust-cbindgen openSUSE Leap 15.2 0.14.1-lp152.2.4.1
  • rust openSUSE Leap 15.2 1.43.1-lp152.3.5.1
  • rust-cbindgen openSUSE Leap 15.1 0.14.1-lp151.8.2
  • rust openSUSE Leap 15.1 1.43.1-lp151.5.13.1

opensuse advisories openSUSE-SU-2024:11127-1openSUSE-SU-2024:11360-1openSUSE-SU-2020:0945-1openSUSE-SU-2020:0933-1

  • openssl Alpine 3.24, Alpine 3.23, Alpine 3.22 +13 more 1.1.1g-r0
  • openssl3 Alpine 3.16, Alpine 3.15 1.1.1g-r0
  • openssl1.1-compat Alpine 3.18, Alpine 3.17 1.1.1g-r0

alpine advisories ALPINE-CVE-2020-1967

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • openssl Arch Linux 1.1.1.g-1
  • lib32-openssl Arch Linux 1.1.1.g-1

arch linux advisories AVG-1139AVG-1142

Is CVE-2020-1967 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-1967 updated cvss 7.5

openssl: Segmentation fault in SSL_check_chain causes denial of service

  • Red Hat Enterprise Linux 5 openssl, openssl097a Red Hat Enterprise Linux 6 openssl, openssl098e, openssl-perl Red Hat Enterprise Linux 7 openssl, openssl098e, openssl-libs, openssl-perl Red Hat Enterprise Linux 8 openssl, openssl-libs, openssl-perl, compat-openssl10 Red Hat JBoss Core Services jbcs-httpd24-openssl Red Hat JBoss Enterprise Application Platform 6 openssl
    +3 more products
    Red Hat JBoss Enterprise Web Server 2 openssl Red Hat JBoss Web Server 3 openssl Red Hat JBoss Web Server 5 openssl
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

cisa ICSA-24-046-02 updated cvss 7.5

Siemens SIDIS Prime

  • Siemens SIDIS Prime <V4.0.400
    affected: fixed in V4.0.400

Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last mo.

Exploit prediction

53.34% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/irsl/CVE-2020-1967 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
crates.io openssl-src
>=111.6.0, <111.9.0
111.9.0
julia OpenSSL_jll
>=1.1.1+2, <1.1.10+0
1.1.10+0

Affected products

  • OpenSSL OpenSSL

Classification

Weakness
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.