security-tracker.debian.org Open in urlscan Pro
2a04:4e42:3::644  Public Scan

Form analysis
1 forms found in the DOM

GET /tracker/

<form method="get" id="searchform" action="/tracker/">Search for package or bug name: <input type="text" name="query" onkeyup="onSearch(this.value)" onmousemove="onSearch(this.value)"><input type="submit" value="Go">
  <a href="/tracker/data/report">Reporting problems</a></form>

Text Content

CVE-2021-3712

NameCVE-2021-3712DescriptionASN.1 strings are represented internally within
OpenSSL as an ASN1_STRING structure which contains a buffer holding the string
data and a field holding the buffer length. This contrasts with normal C strings
which are repesented as a buffer for the string data which is terminated with a
NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed
using OpenSSL's own "d2i" functions (and other similar parsing functions) as
well as any string whose value has been set with the ASN1_STRING_set() function
will additionally NUL terminate the byte array in the ASN1_STRING structure.
However, it is possible for applications to directly construct valid ASN1_STRING
structures which do not NUL terminate the byte array by directly setting the
"data" and "length" fields in the ASN1_STRING array. This can also happen by
using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print
ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL
terminated, even though this is not guaranteed for strings that have been
directly constructed. Where an application requests an ASN.1 structure to be
printed, and where that ASN.1 structure contains ASN1_STRINGs that have been
directly constructed by the application without NUL terminating the "data"
field, then a read buffer overrun can occur. The same thing can also occur
during name constraints processing of certificates (for example if a certificate
has been directly constructed by the application instead of loading it via the
OpenSSL parsing functions, and the certificate contains non NUL terminated
ASN1_STRING structures). It can also occur in the X509_get1_email(),
X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can
cause an application to directly construct an ASN1_STRING and then process it
through one of the affected OpenSSL functions then this issue could be hit. This
might result in a crash (causing a Denial of Service attack). It could also
result in the disclosure of private memory contents (such as private keys, or
sensitive plaintext). Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). Fixed in
OpenSSL 1.0.2za (Affected 1.0.2-1.0.2y).SourceCVE (at NVD; CERT, LWN, oss-sec,
fulldisc, bugtraq, EDB, Metasploit, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE,
Mageia, GitHub code/issues, web search, more)ReferencesDLA-2766-1, DLA-2774-1,
DSA-4963-1NVD severitymedium


VULNERABLE AND FIXED PACKAGES

The table below lists information on source packages.

Source PackageReleaseVersionStatusopenssl
(PTS)stretch1.1.0l-1~deb9u1vulnerablestretch
(security)1.1.0l-1~deb9u5fixedbuster1.1.1n-0+deb10u1fixedbuster
(security)1.1.1d-0+deb10u8fixedbullseye1.1.1n-0+deb11u1fixedbullseye
(security)1.1.1k-1+deb11u2fixedbookworm, sid1.1.1n-1fixedopenssl1.0
(PTS)stretch1.0.2u-1~deb9u1vulnerablestretch (security)1.0.2u-1~deb9u7fixed

The information below is based on the following data on fixed versions.

PackageTypeReleaseFixed VersionUrgencyOriginDebian
Bugsopensslsourcestretch1.1.0l-1~deb9u4DLA-2766-1opensslsourcebuster1.1.1d-0+deb10u7DSA-4963-1opensslsourcebullseye1.1.1k-1+deb11u1DSA-4963-1opensslsource(unstable)1.1.1l-1openssl1.0sourcestretch1.0.2u-1~deb9u6DLA-2774-1openssl1.0source(unstable)(unfixed)


NOTES

https://www.openssl.org/news/secadv/20210824.txt
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=d9d838ddc0ed083fb4c26dd067e71aad7c65ad16 (OpenSSL_1_1_1l)
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=174ba8048a7f2f5e1fca31cfb93b1730d9db8300 (OpenSSL_1_1_1l)
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=5f54e57406ca17731b9ade3afd561d3c652e07f2 (OpenSSL_1_1_1l)
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=23446958685a593d4d9434475734b99138902ed2 (OpenSSL_1_1_1l)
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=8393de42498f8be75cf0353f5c9f906a43a748d2 (OpenSSL_1_1_1l)
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=4de66925203ca99189c842136ec4a623137ea447 (OpenSSL_1_1_1l)
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=bb4d2ed4091408404e18b3326e3df67848ef63d0 (OpenSSL_1_1_1l)
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=2d0e5d4a4a5d4332325b5e5cea492fad2be633e1 (OpenSSL_1_1_1l)
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=94d23fcff9b2a7a8368dfe52214d5c2569882c11 (OpenSSL_1_1_1l)
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=8c74c9d1ade0fbdab5b815ddb747351b8b839641 (OpenSSL_1_1_1l)


--------------------------------------------------------------------------------

Search for package or bug name: Reporting problems

Home - Debian Security - Source (Git)