Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

oracle-oval логотип

ELSA-2021-5226

Опубликовано: 22 дек. 2021
Источник: oracle-oval
Платформа: Oracle Linux 8

Описание

ELSA-2021-5226: openssl security update (MODERATE)

[1:1.1.1k-5]

  • CVE-2021-3712 openssl: Read buffer overruns processing ASN.1 strings
  • Resolves: rhbz#2005400

Обновленные пакеты

Oracle Linux 8

Oracle Linux aarch64

openssl

1.1.1k-5.el8_5

openssl-devel

1.1.1k-5.el8_5

openssl-libs

1.1.1k-5.el8_5

openssl-perl

1.1.1k-5.el8_5

Oracle Linux x86_64

openssl

1.1.1k-5.el8_5

openssl-devel

1.1.1k-5.el8_5

openssl-libs

1.1.1k-5.el8_5

openssl-perl

1.1.1k-5.el8_5

Связанные CVE

Связанные уязвимости

CVSS3: 7.4
ubuntu
почти 4 года назад

ASN.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 ter...

CVSS3: 7.4
redhat
почти 4 года назад

ASN.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 ter...

CVSS3: 7.4
nvd
почти 4 года назад

ASN.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 termin

CVSS3: 7.4
msrc
больше 3 лет назад

Описание отсутствует

CVSS3: 7.4
debian
почти 4 года назад

ASN.1 strings are represented internally within OpenSSL as an ASN1_STR ...