Search for packages
| purl | pkg:openssl/openssl@1.1.1f |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-5khv-27u8-aaaa
Aliases: CVE-2022-2097 GHSA-3wx7-46ch-7rq2 VC-OPENSSL-20220705-CVE-2022-2097 |
AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimised implementation will not encrypt the entirety of the data under some circumstances. This could reveal sixteen bytes of data that was preexisting in the memory that wasn't written. In the special case of "in place" encryption, sixteen bytes of the plaintext would be revealed. Since OpenSSL does not support OCB based cipher suites for TLS and DTLS, they are both unaffected. Fixed in OpenSSL 3.0.5 (Affected 3.0.0-3.0.4). Fixed in OpenSSL 1.1.1q (Affected 1.1.1-1.1.1p). |
Affected by 0 other vulnerabilities. Affected by 3 other vulnerabilities. |
|
VCID-6cjv-xp17-aaah
Aliases: CVE-2021-3449 GHSA-83mx-573x-5rw9 VC-OPENSSL-20210325-CVE-2021-3449 |
An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. If a TLSv1.2 renegotiation ClientHello omits the signature_algorithms extension (where it was present in the initial ClientHello), but includes a signature_algorithms_cert extension then a NULL pointer dereference will result, leading to a crash and a denial of service attack. A server is only vulnerable if it has TLSv1.2 and renegotiation enabled (which is the default configuration). OpenSSL TLS clients are not impacted by this issue. All OpenSSL 1.1.1 versions are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1-1.1.1j). |
Affected by 7 other vulnerabilities. |
|
VCID-6pjh-cgdt-aaaj
Aliases: CVE-2022-0778 GHSA-x3mh-jvjw-3xwx VC-OPENSSL-20220315-CVE-2022-0778 |
The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop forever for non-prime moduli. Internally this function is used when parsing certificates that contain elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point encoded in compressed form. It is possible to trigger the infinite loop by crafting a certificate that has invalid explicit curve parameters. Since certificate parsing happens prior to verification of the certificate signature, any process that parses an externally supplied certificate may thus be subject to a denial of service attack. The infinite loop can also be reached when parsing crafted private keys as they can contain explicit elliptic curve parameters. Thus vulnerable situations include: - TLS clients consuming server certificates - TLS servers consuming client certificates - Hosting providers taking certificates or private keys from customers - Certificate authorities parsing certification requests from subscribers - Anything else which parses ASN.1 elliptic curve parameters Also any other applications that use the BN_mod_sqrt() where the attacker can control the parameter values are vulnerable to this DoS issue. In the OpenSSL 1.0.2 version the public key is not parsed during initial parsing of the certificate which makes it slightly harder to trigger the infinite loop. However any operation which requires the public key from the certificate will trigger the infinite loop. In particular the attacker can use a self-signed certificate to trigger the loop during verification of the certificate signature. This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0. It was addressed in the releases of 1.1.1n and 3.0.2 on the 15th March 2022. Fixed in OpenSSL 3.0.2 (Affected 3.0.0,3.0.1). Fixed in OpenSSL 1.1.1n (Affected 1.1.1-1.1.1m). Fixed in OpenSSL 1.0.2zd (Affected 1.0.2-1.0.2zc). |
Affected by 3 other vulnerabilities. Affected by 9 other vulnerabilities. |
|
VCID-7bwv-hdm1-aaae
Aliases: CVE-2020-1967 GHSA-jq65-29v4-4x35 VC-OPENSSL-20200421-CVE-2020-1967 |
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). |
Affected by 11 other vulnerabilities. |
|
VCID-9ruy-372r-aaas
Aliases: CVE-2021-23841 GHSA-84rm-qf37-fgc2 VC-OPENSSL-20210216-CVE-2021-23841 |
The OpenSSL public API function X509_issuer_and_serial_hash() attempts to create a unique hash value based on the issuer and serial number data contained within an X509 certificate. However it fails to correctly handle any errors that may occur while parsing the issuer field (which might occur if the issuer field is maliciously constructed). This may subsequently result in a NULL pointer deref and a crash leading to a potential denial of service attack. The function X509_issuer_and_serial_hash() is never directly called by OpenSSL itself so applications are only vulnerable if they use this function directly and they use it on certificates that may have been obtained from untrusted sources. OpenSSL versions 1.1.1i and below are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1j. OpenSSL versions 1.0.2x and below are affected by this issue. However OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i). Fixed in OpenSSL 1.0.2y (Affected 1.0.2-1.0.2x). |
Affected by 9 other vulnerabilities. |
|
VCID-ghgs-7167-aaag
Aliases: CVE-2021-3712 GHSA-q9wj-f4qw-6vfj VC-OPENSSL-20210824-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 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). |
Affected by 5 other vulnerabilities. |
|
VCID-nx9u-49dk-aaag
Aliases: CVE-2020-1971 VC-OPENSSL-20201208-CVE-2020-1971 |
Affected by 11 other vulnerabilities. |
|
|
VCID-qtbw-vpbp-aaaj
Aliases: CVE-2021-4160 VC-OPENSSL-20220128-CVE-2021-4160 |
There is a carry propagation bug in the MIPS32 and MIPS64 squaring procedure. Many EC algorithms are affected, including some of the TLS 1.3 default curves. Impact was not analyzed in detail, because the pre-requisites for attack are considered unlikely and include reusing private keys. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH are considered just feasible (although very difficult) because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be significant. However, for an attack on TLS to be meaningful, the server would have to share the DH private key among multiple clients, which is no longer an option since CVE-2016-0701. This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0.0. It was addressed in the releases of 1.1.1m and 3.0.1 on the 15th of December 2021. For the 1.0.2 release it is addressed in git commit 6fc1aaaf3 that is available to premium support customers only. It will be made available in 1.0.2zc when it is released. The issue only affects OpenSSL on MIPS platforms. |
Affected by 4 other vulnerabilities. Affected by 10 other vulnerabilities. |
|
VCID-r7qs-74zt-aaab
Aliases: CVE-2021-3711 GHSA-5ww6-px42-wc85 VC-OPENSSL-20210824-CVE-2021-3711 |
In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Typically an application will call this function twice. The first time, on entry, the "out" parameter can be NULL and, on exit, the "outlen" parameter is populated with the buffer size required to hold the decrypted plaintext. The application can then allocate a sufficiently sized buffer and call EVP_PKEY_decrypt() again, but this time passing a non-NULL value for the "out" parameter. A bug in the implementation of the SM2 decryption code means that the calculation of the buffer size required to hold the plaintext returned by the first call to EVP_PKEY_decrypt() can be smaller than the actual size required by the second call. This can lead to a buffer overflow when EVP_PKEY_decrypt() is called by the application a second time with a buffer that is too small. A malicious attacker who is able present SM2 content for decryption to an application could cause attacker chosen data to overflow the buffer by up to a maximum of 62 bytes altering the contents of other data held after the buffer, possibly changing application behaviour or causing the application to crash. The location of the buffer is application dependent but is typically heap allocated. Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). |
Affected by 5 other vulnerabilities. |
|
VCID-vc4y-g9fg-aaak
Aliases: CVE-2021-23840 GHSA-qgm6-9472-pwq7 VC-OPENSSL-20210216-CVE-2021-23840 |
Calls to EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument in some cases where the input length is close to the maximum permissable length for an integer on the platform. In such cases the return value from the function call will be 1 (indicating success), but the output length value will be negative. This could cause applications to behave incorrectly or crash. OpenSSL versions 1.1.1i and below are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1j. OpenSSL versions 1.0.2x and below are affected by this issue. However OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i). Fixed in OpenSSL 1.0.2y (Affected 1.0.2-1.0.2x). |
Affected by 9 other vulnerabilities. |
|
VCID-w17h-u8wd-aaaj
Aliases: CVE-2022-2068 VC-OPENSSL-20220621-CVE-2022-2068 |
In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehash script does not properly sanitise shell metacharacters to prevent command injection were found by code review. When the CVE-2022-1292 was fixed it was not discovered that there are other places in the script where the file names of certificates being hashed were possibly passed to a command executed through the shell. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.4 (Affected 3.0.0,3.0.1,3.0.2,3.0.3). Fixed in OpenSSL 1.1.1p (Affected 1.1.1-1.1.1o). Fixed in OpenSSL 1.0.2zf (Affected 1.0.2-1.0.2ze). |
Affected by 1 other vulnerability. Affected by 5 other vulnerabilities. |
|
VCID-yrx6-rcrr-aaap
Aliases: CVE-2022-1292 VC-OPENSSL-20220503-CVE-2022-1292 |
The c_rehash script does not properly sanitise shell metacharacters to prevent command injection. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). Fixed in OpenSSL 1.1.1o (Affected 1.1.1-1.1.1n). Fixed in OpenSSL 1.0.2ze (Affected 1.0.2-1.0.2zd). |
Affected by 2 other vulnerabilities. Affected by 5 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||
| Date | Actor | Action | Vulnerability | Source | VulnerableCode Version |
|---|---|---|---|---|---|
| 2024-01-03T20:01:28.369464+00:00 | OpenSSL Importer | Affected by | VCID-7bwv-hdm1-aaae | https://www.openssl.org/news/secadv/20200421.txt | 34.0.0rc1 |
| 2024-01-03T20:01:28.049119+00:00 | OpenSSL Importer | Affected by | VCID-nx9u-49dk-aaag | https://www.openssl.org/news/secadv/20201208.txt | 34.0.0rc1 |
| 2024-01-03T20:01:27.817036+00:00 | OpenSSL Importer | Affected by | VCID-vc4y-g9fg-aaak | https://www.openssl.org/news/secadv/20210216.txt | 34.0.0rc1 |
| 2024-01-03T20:01:27.545540+00:00 | OpenSSL Importer | Affected by | VCID-9ruy-372r-aaas | https://www.openssl.org/news/secadv/20210216.txt | 34.0.0rc1 |
| 2024-01-03T20:01:27.463133+00:00 | OpenSSL Importer | Affected by | VCID-6cjv-xp17-aaah | https://www.openssl.org/news/secadv/20210325.txt | 34.0.0rc1 |
| 2024-01-03T20:01:27.197506+00:00 | OpenSSL Importer | Affected by | VCID-ghgs-7167-aaag | https://www.openssl.org/news/secadv/20210824.txt | 34.0.0rc1 |
| 2024-01-03T20:01:27.114043+00:00 | OpenSSL Importer | Affected by | VCID-r7qs-74zt-aaab | https://www.openssl.org/news/secadv/20210824.txt | 34.0.0rc1 |
| 2024-01-03T20:01:26.850766+00:00 | OpenSSL Importer | Affected by | VCID-qtbw-vpbp-aaaj | https://www.openssl.org/news/secadv/20220128.txt | 34.0.0rc1 |
| 2024-01-03T20:01:26.569838+00:00 | OpenSSL Importer | Affected by | VCID-6pjh-cgdt-aaaj | https://www.openssl.org/news/secadv/20220315.txt | 34.0.0rc1 |
| 2024-01-03T20:01:26.171423+00:00 | OpenSSL Importer | Affected by | VCID-yrx6-rcrr-aaap | https://www.openssl.org/news/secadv/20220503.txt | 34.0.0rc1 |
| 2024-01-03T20:01:25.858934+00:00 | OpenSSL Importer | Affected by | VCID-w17h-u8wd-aaaj | https://www.openssl.org/news/secadv/20220621.txt | 34.0.0rc1 |
| 2024-01-03T20:01:25.675906+00:00 | OpenSSL Importer | Affected by | VCID-5khv-27u8-aaaa | https://www.openssl.org/news/secadv/20220705.txt | 34.0.0rc1 |