Количество 1 688
Количество 1 688
SUSE-SU-2021:14791-1
Security update for openssl
RLSA-2021:5226
Moderate: openssl security update
GHSA-q9wj-f4qw-6vfj
Read buffer overruns processing ASN.1 strings
ELSA-2022-9023
ELSA-2022-9023: openssl security update (MODERATE)
ELSA-2022-9017
ELSA-2022-9017: openssl security update (MODERATE)
ELSA-2022-0064
ELSA-2022-0064: openssl security update (MODERATE)
ELSA-2021-9632
ELSA-2021-9632: openssl security update (MODERATE)
ELSA-2021-5226
ELSA-2021-5226: openssl security update (MODERATE)
CVE-2021-3712
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...
CVE-2021-3712
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...
CVE-2021-3712
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
CVE-2021-3712
ASN.1 strings are represented internally within OpenSSL as an ASN1_STR ...
openSUSE-SU-2020:2269-1
Security update for openssl-1_0_0
openSUSE-SU-2020:2245-1
Security update for openssl-1_1
openSUSE-SU-2020:2236-1
Security update for openssl-1_0_0
openSUSE-SU-2020:2223-1
Security update for openssl-1_1
SUSE-SU-2020:3763-1
Security update for openssl
SUSE-SU-2020:3762-1
Security update for openssl-1_0_0
SUSE-SU-2020:3740-1
Security update for openssl-1_1
SUSE-SU-2020:3732-1
Security update for openssl-1_0_0
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
SUSE-SU-2021:14791-1 Security update for openssl | 50% Средний | около 5 лет назад | ||
RLSA-2021:5226 Moderate: openssl security update | 50% Средний | больше 4 лет назад | ||
GHSA-q9wj-f4qw-6vfj Read buffer overruns processing ASN.1 strings | CVSS3: 7.4 | 50% Средний | больше 4 лет назад | |
ELSA-2022-9023 ELSA-2022-9023: openssl security update (MODERATE) | 50% Средний | больше 4 лет назад | ||
ELSA-2022-9017 ELSA-2022-9017: openssl security update (MODERATE) | 50% Средний | больше 4 лет назад | ||
ELSA-2022-0064 ELSA-2022-0064: openssl security update (MODERATE) | 50% Средний | больше 4 лет назад | ||
ELSA-2021-9632 ELSA-2021-9632: openssl security update (MODERATE) | 50% Средний | больше 4 лет назад | ||
ELSA-2021-5226 ELSA-2021-5226: openssl security update (MODERATE) | 50% Средний | больше 4 лет назад | ||
CVE-2021-3712 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 | 50% Средний | около 5 лет назад | |
CVE-2021-3712 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 | 50% Средний | около 5 лет назад | |
CVE-2021-3712 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 | 50% Средний | около 5 лет назад | |
CVE-2021-3712 ASN.1 strings are represented internally within OpenSSL as an ASN1_STR ... | CVSS3: 7.4 | 50% Средний | около 5 лет назад | |
openSUSE-SU-2020:2269-1 Security update for openssl-1_0_0 | 7% Низкий | больше 5 лет назад | ||
openSUSE-SU-2020:2245-1 Security update for openssl-1_1 | 7% Низкий | почти 6 лет назад | ||
openSUSE-SU-2020:2236-1 Security update for openssl-1_0_0 | 7% Низкий | почти 6 лет назад | ||
openSUSE-SU-2020:2223-1 Security update for openssl-1_1 | 7% Низкий | почти 6 лет назад | ||
SUSE-SU-2020:3763-1 Security update for openssl | 7% Низкий | почти 6 лет назад | ||
SUSE-SU-2020:3762-1 Security update for openssl-1_0_0 | 7% Низкий | почти 6 лет назад | ||
SUSE-SU-2020:3740-1 Security update for openssl-1_1 | 7% Низкий | почти 6 лет назад | ||
SUSE-SU-2020:3732-1 Security update for openssl-1_0_0 | 7% Низкий | почти 6 лет назад |
Уязвимостей на страницу