Search for packages
| purl | pkg:openssl/openssl@1.0.2j |
| Next non-vulnerable version | 1.0.2zc-de |
| Latest non-vulnerable version | 3.0.7 |
| Risk | 10.0 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-1gxv-1j1x-aaag
Aliases: CVE-2019-1547 VC-OPENSSL-20190910-CVE-2019-1547 |
Normally in OpenSSL EC groups always have a co-factor present and this is used in side channel resistant code paths. However, in some cases, it is possible to construct a group using explicit parameters (instead of using a named curve). In those cases it is possible that such a group does not have the cofactor present. This can occur even where all the parameters match a known named curve. If such a curve is used then OpenSSL falls back to non-side channel resistant code paths which may result in full key recovery during an ECDSA signature operation. In order to be vulnerable an attacker would have to have the ability to time the creation of a large number of signatures where explicit parameters with no co-factor present are in use by an application using libcrypto. For the avoidance of doubt libssl is not vulnerable because explicit parameters are never used. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s). |
Affected by 11 other vulnerabilities. Affected by 0 other vulnerabilities. Affected by 13 other vulnerabilities. |
|
VCID-4hq6-j84v-aaan
Aliases: CVE-2017-3738 VC-OPENSSL-20171207-CVE-2017-3738 |
There is an overflow bug in the AVX2 Montgomery multiplication procedure used in exponentiation with 1024-bit moduli. No EC algorithms are affected. 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 DH1024 are considered just feasible, 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 DH1024 private key among multiple clients, which is no longer an option since CVE-2016-0701. This only affects processors that support the AVX2 but not ADX extensions like Intel Haswell (4th generation). Note: The impact from this issue is similar to CVE-2017-3736, CVE-2017-3732 and CVE-2015-3193. OpenSSL version 1.0.2-1.0.2m and 1.1.0-1.1.0g are affected. Fixed in OpenSSL 1.0.2n. Due to the low severity of this issue we are not issuing a new release of OpenSSL 1.1.0 at this time. The fix will be included in OpenSSL 1.1.0h when it becomes available. The fix is also available in commit e502cc86d in the OpenSSL git repository. |
Affected by 19 other vulnerabilities. Affected by 9 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 2 other vulnerabilities. Affected by 3 other vulnerabilities. Affected by 9 other vulnerabilities. |
|
VCID-9cyz-en38-aaad
Aliases: CVE-2018-0732 VC-OPENSSL-20180612-CVE-2018-0732 |
During key agreement in a TLS handshake using a DH(E) based ciphersuite a malicious server can send a very large prime value to the client. This will cause the client to spend an unreasonably long period of time generating a key for this prime resulting in a hang until the client has finished. This could be exploited in a Denial Of Service attack. Fixed in OpenSSL 1.1.0i-dev (Affected 1.1.0-1.1.0h). Fixed in OpenSSL 1.0.2p-dev (Affected 1.0.2-1.0.2o). |
Affected by 16 other vulnerabilities. Affected by 6 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 5 other vulnerabilities. Affected by 9 other vulnerabilities. |
|
VCID-ceua-4xhz-aaag
Aliases: CVE-2018-5407 VC-OPENSSL-20181102-CVE-2018-5407 |
Simultaneous Multi-threading (SMT) in processors can enable local users to exploit software vulnerable to timing attacks via a side-channel timing attack on 'port contention'. |
Affected by 14 other vulnerabilities. Affected by 6 other vulnerabilities. |
|
VCID-fmvb-j6br-aaap
Aliases: CVE-2018-0739 VC-OPENSSL-20180327-CVE-2018-0739 |
Constructed ASN.1 types with a recursive definition (such as can be found in PKCS7) could eventually exceed the stack given malicious input with excessive recursion. This could result in a Denial Of Service attack. There are no such structures used within SSL/TLS that come from untrusted sources so this is considered safe. Fixed in OpenSSL 1.1.0h (Affected 1.1.0-1.1.0g). Fixed in OpenSSL 1.0.2o (Affected 1.0.2b-1.0.2n). |
Affected by 18 other vulnerabilities. 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 4 other vulnerabilities. Affected by 5 other vulnerabilities. |
|
VCID-j8pb-xdpc-aaap
Aliases: CVE-2018-0737 VC-OPENSSL-20180416-CVE-2018-0737 |
The OpenSSL RSA Key generation algorithm has been shown to be vulnerable to a cache timing side channel attack. An attacker with sufficient access to mount cache timing attacks during the RSA key generation process could recover the private key. Fixed in OpenSSL 1.1.0i-dev (Affected 1.1.0-1.1.0h). Fixed in OpenSSL 1.0.2p-dev (Affected 1.0.2b-1.0.2o). |
Affected by 16 other vulnerabilities. Affected by 6 other vulnerabilities. |
|
VCID-jhg8-wbm2-aaas
Aliases: CVE-2017-3735 VC-OPENSSL-20170828-CVE-2017-3735 |
While parsing an IPAddressFamily extension in an X.509 certificate, it is possible to do a one-byte overread. This would result in an incorrect text display of the certificate. This bug has been present since 2006 and is present in all versions of OpenSSL before 1.0.2m and 1.1.0g. |
Affected by 21 other vulnerabilities. Affected by 12 other vulnerabilities. |
|
VCID-msmt-6x6r-aaaj
Aliases: CVE-2020-1968 VC-OPENSSL-20200909-CVE-2020-1968 |
The Raccoon attack exploits a flaw in the TLS specification which can lead to an attacker being able to compute the pre-master secret in connections which have used a Diffie-Hellman (DH) based ciphersuite. In such a case this would result in the attacker being able to eavesdrop on all encrypted communications sent over that TLS connection. The attack can only be exploited if an implementation re-uses a DH secret across multiple TLS connections. Note that this issue only impacts DH ciphersuites and not ECDH ciphersuites. This issue affects OpenSSL 1.0.2 which is out of support and no longer receiving public updates. OpenSSL 1.1.1 is not vulnerable to this issue. |
Affected by 9 other vulnerabilities. |
|
VCID-nx9u-49dk-aaag
Aliases: CVE-2020-1971 VC-OPENSSL-20201208-CVE-2020-1971 |
Affected by 8 other vulnerabilities. Affected by 11 other vulnerabilities. |
|
|
VCID-psvb-thr2-aaap
Aliases: CVE-2018-0734 VC-OPENSSL-20181030-CVE-2018-0734 |
The OpenSSL DSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.1a (Affected 1.1.1). Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.0.2q (Affected 1.0.2-1.0.2p). |
Affected by 14 other vulnerabilities. Affected by 4 other vulnerabilities. Affected by 17 other vulnerabilities. |
|
VCID-pzng-q94v-aaah
Aliases: CVE-2019-1552 VC-OPENSSL-20190730-CVE-2019-1552 |
OpenSSL has internal defaults for a directory tree where it can find a configuration file as well as certificates used for verification in TLS. This directory is most commonly referred to as OPENSSLDIR, and is configurable with the --prefix / --openssldir configuration options. For OpenSSL versions 1.1.0 and 1.1.1, the mingw configuration targets assume that resulting programs and libraries are installed in a Unix-like environment and the default prefix for program installation as well as for OPENSSLDIR should be '/usr/local'. However, mingw programs are Windows programs, and as such, find themselves looking at sub-directories of 'C:/usr/local', which may be world writable, which enables untrusted users to modify OpenSSL's default configuration, insert CA certificates, modify (or even replace) existing engine modules, etc. For OpenSSL 1.0.2, '/usr/local/ssl' is used as default for OPENSSLDIR on all Unix and Windows targets, including Visual C builds. However, some build instructions for the diverse Windows targets on 1.0.2 encourage you to specify your own --prefix. OpenSSL versions 1.1.1, 1.1.0 and 1.0.2 are affected by this issue. Due to the limited scope of affected deployments this has been assessed as low severity and therefore we are not creating new releases at this time. |
Affected by 11 other vulnerabilities. Affected by 0 other vulnerabilities. Affected by 13 other vulnerabilities. |
|
VCID-q9r2-dz2p-aaap
Aliases: CVE-2019-1563 VC-OPENSSL-20190910-CVE-2019-1563 |
In situations where an attacker receives automated notification of the success or failure of a decryption attempt an attacker, after sending a very large number of messages to be decrypted, can recover a CMS/PKCS7 transported encryption key or decrypt any RSA encrypted message that was encrypted with the public RSA key, using a Bleichenbacher padding oracle attack. Applications are not affected if they use a certificate together with the private RSA key to the CMS_decrypt or PKCS7_decrypt functions to select the correct recipient info to decrypt. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s). |
Affected by 11 other vulnerabilities. Affected by 0 other vulnerabilities. Affected by 13 other vulnerabilities. |
|
VCID-qkh6-sakf-aaar
Aliases: CVE-2017-3732 VC-OPENSSL-20170126-CVE-2017-3732 |
There is a carry propagating bug in the x86_64 Montgomery squaring procedure in OpenSSL 1.0.2 before 1.0.2k and 1.1.0 before 1.1.0d. No EC algorithms are affected. 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 very significant and likely only accessible to a limited number of attackers. An attacker would additionally need online access to an unpatched system using the target private key in a scenario with persistent DH parameters and a private key that is shared between multiple clients. For example this can occur by default in OpenSSL DHE based SSL/TLS ciphersuites. Note: This issue is very similar to CVE-2015-3193 but must be treated as a separate problem. |
Affected by 23 other vulnerabilities. Affected by 15 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 3 other vulnerabilities. Affected by 0 other vulnerabilities. Affected by 4 other vulnerabilities. Affected by 10 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 5 other vulnerabilities. Affected by 9 other vulnerabilities. |
|
VCID-vm2m-bf4p-aaaf
Aliases: CVE-2019-1559 VC-OPENSSL-20190226-CVE-2019-1559 |
Affected by 13 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 0 other vulnerabilities. Affected by 1 other vulnerability. Affected by 5 other vulnerabilities. |
|
VCID-w3xz-a1z2-aaaf
Aliases: CVE-2017-3731 VC-OPENSSL-20170126-CVE-2017-3731 |
If an SSL/TLS server or client is running on a 32-bit host, and a specific cipher is being used, then a truncated packet can cause that server or client to perform an out-of-bounds read, usually resulting in a crash. For OpenSSL 1.1.0, the crash can be triggered when using CHACHA20/POLY1305; users should upgrade to 1.1.0d. For Openssl 1.0.2, the crash can be triggered when using RC4-MD5; users who have not disabled that algorithm should update to 1.0.2k. |
Affected by 23 other vulnerabilities. Affected by 15 other vulnerabilities. |
|
VCID-y2q8-1hgf-aaak
Aliases: CVE-2019-1551 VC-OPENSSL-20191206-CVE-2019-1551 |
There is an overflow bug in the x64_64 Montgomery squaring procedure used in exponentiation with 512-bit moduli. No EC algorithms are affected. Analysis suggests that attacks against 2-prime RSA1024, 3-prime RSA1536, and DSA1024 as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH512 are considered just feasible. However, for an attack the target would have to re-use the DH512 private key, which is not recommended anyway. Also applications directly using the low level API BN_mod_exp may be affected if they use BN_FLG_CONSTTIME. Fixed in OpenSSL 1.1.1e (Affected 1.1.1-1.1.1d). Fixed in OpenSSL 1.0.2u (Affected 1.0.2-1.0.2t). |
Affected by 10 other vulnerabilities. Affected by 12 other vulnerabilities. |
|
VCID-y471-3h22-aaah
Aliases: CVE-2016-7055 VC-OPENSSL-20161110-CVE-2016-7055 |
There is a carry propagating bug in the Broadwell-specific Montgomery multiplication procedure in OpenSSL 1.0.2 and 1.1.0 before 1.1.0c that handles input lengths divisible by, but longer than 256 bits. Analysis suggests that attacks against RSA, DSA and DH private keys are impossible. This is because the subroutine in question is not used in operations with the private key itself and an input of the attacker's direct choice. Otherwise the bug can manifest itself as transient authentication and key negotiation failures or reproducible erroneous outcome of public-key operations with specially crafted input. Among EC algorithms only Brainpool P-512 curves are affected and one presumably can attack ECDH key negotiation. Impact was not analyzed in detail, because pre-requisites for attack are considered unlikely. Namely multiple clients have to choose the curve in question and the server has to share the private key among them, neither of which is default behaviour. Even then only clients that chose the curve will be affected. |
Affected by 23 other vulnerabilities. Affected by 18 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 1 other vulnerability. Affected by 2 other vulnerabilities. Affected by 5 other vulnerabilities. |
|
VCID-ys3w-wua9-aaas
Aliases: CVE-2017-3736 VC-OPENSSL-20171102-CVE-2017-3736 |
There is a carry propagating bug in the x86_64 Montgomery squaring procedure in OpenSSL before 1.0.2m and 1.1.0 before 1.1.0g. No EC algorithms are affected. 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 very significant and likely only accessible to a limited number of attackers. An attacker would additionally need online access to an unpatched system using the target private key in a scenario with persistent DH parameters and a private key that is shared between multiple clients. This only affects processors that support the BMI1, BMI2 and ADX extensions like Intel Broadwell (5th generation) and later or AMD Ryzen. |
Affected by 21 other vulnerabilities. Affected by 12 other vulnerabilities. |
|
VCID-zesf-f628-aaad
Aliases: CVE-2017-3737 VC-OPENSSL-20171207-CVE-2017-3737 |
OpenSSL 1.0.2 (starting from version 1.0.2b) introduced an "error state" mechanism. The intent was that if a fatal error occurred during a handshake then OpenSSL would move into the error state and would immediately fail if you attempted to continue the handshake. This works as designed for the explicit handshake functions (SSL_do_handshake(), SSL_accept() and SSL_connect()), however due to a bug it does not work correctly if SSL_read() or SSL_write() is called directly. In that scenario, if the handshake fails then a fatal error will be returned in the initial function call. If SSL_read()/SSL_write() is subsequently called by the application for the same SSL object then it will succeed and the data is passed without being decrypted/encrypted directly from the SSL/TLS record layer. In order to exploit this issue an application bug would have to be present that resulted in a call to SSL_read()/SSL_write() being issued after having already received a fatal error. OpenSSL version 1.0.2b-1.0.2m are affected. Fixed in OpenSSL 1.0.2n. OpenSSL 1.1.0 is not affected. |
Affected by 19 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-7e6q-x9ge-aaas | crypto/x509/x509_vfy.c in OpenSSL 1.0.2i allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) by triggering a CRL operation. |
CVE-2016-7052
VC-OPENSSL-20160926-CVE-2016-7052 |
| Date | Actor | Action | Vulnerability | Source | VulnerableCode Version |
|---|---|---|---|---|---|
| 2024-01-03T20:01:31.751142+00:00 | OpenSSL Importer | Fixing | VCID-7e6q-x9ge-aaas | https://www.openssl.org/news/secadv/20160926.txt | 34.0.0rc1 |
| 2024-01-03T20:01:31.688123+00:00 | OpenSSL Importer | Affected by | VCID-y471-3h22-aaah | https://www.openssl.org/news/secadv/20161110.txt | 34.0.0rc1 |
| 2024-01-03T20:01:31.431428+00:00 | OpenSSL Importer | Affected by | VCID-qkh6-sakf-aaar | https://www.openssl.org/news/secadv/20170126.txt | 34.0.0rc1 |
| 2024-01-03T20:01:31.273635+00:00 | OpenSSL Importer | Affected by | VCID-w3xz-a1z2-aaaf | https://www.openssl.org/news/secadv/20170126.txt | 34.0.0rc1 |
| 2024-01-03T20:01:31.096340+00:00 | OpenSSL Importer | Affected by | VCID-jhg8-wbm2-aaas | https://www.openssl.org/news/secadv/20170828.txt | 34.0.0rc1 |
| 2024-01-03T20:01:30.946704+00:00 | OpenSSL Importer | Affected by | VCID-ys3w-wua9-aaas | https://www.openssl.org/news/secadv/20171102.txt | 34.0.0rc1 |
| 2024-01-03T20:01:30.797708+00:00 | OpenSSL Importer | Affected by | VCID-4hq6-j84v-aaan | https://www.openssl.org/news/secadv/20171207.txt | 34.0.0rc1 |
| 2024-01-03T20:01:30.644189+00:00 | OpenSSL Importer | Affected by | VCID-zesf-f628-aaad | https://www.openssl.org/news/secadv/20171207.txt | 34.0.0rc1 |
| 2024-01-03T20:01:30.491236+00:00 | OpenSSL Importer | Affected by | VCID-fmvb-j6br-aaap | https://www.openssl.org/news/secadv/20180327.txt | 34.0.0rc1 |
| 2024-01-03T20:01:30.336152+00:00 | OpenSSL Importer | Affected by | VCID-j8pb-xdpc-aaap | https://www.openssl.org/news/secadv/20180416.txt | 34.0.0rc1 |
| 2024-01-03T20:01:30.174190+00:00 | OpenSSL Importer | Affected by | VCID-9cyz-en38-aaad | https://www.openssl.org/news/secadv/20180612.txt | 34.0.0rc1 |
| 2024-01-03T20:01:29.904592+00:00 | OpenSSL Importer | Affected by | VCID-psvb-thr2-aaap | https://www.openssl.org/news/secadv/20181030.txt | 34.0.0rc1 |
| 2024-01-03T20:01:29.693019+00:00 | OpenSSL Importer | Affected by | VCID-ceua-4xhz-aaag | https://www.openssl.org/news/secadv/20181112.txt | 34.0.0rc1 |
| 2024-01-03T20:01:29.512808+00:00 | OpenSSL Importer | Affected by | VCID-vm2m-bf4p-aaaf | https://www.openssl.org/news/secadv/20190226.txt | 34.0.0rc1 |
| 2024-01-03T20:01:29.285423+00:00 | OpenSSL Importer | Affected by | VCID-pzng-q94v-aaah | https://www.openssl.org/news/secadv/20190730.txt | 34.0.0rc1 |
| 2024-01-03T20:01:29.033526+00:00 | OpenSSL Importer | Affected by | VCID-q9r2-dz2p-aaap | https://www.openssl.org/news/secadv/20190910.txt | 34.0.0rc1 |
| 2024-01-03T20:01:28.740905+00:00 | OpenSSL Importer | Affected by | VCID-1gxv-1j1x-aaag | https://www.openssl.org/news/secadv/20190910.txt | 34.0.0rc1 |
| 2024-01-03T20:01:28.492208+00:00 | OpenSSL Importer | Affected by | VCID-y2q8-1hgf-aaak | https://www.openssl.org/news/secadv/20191206.txt | 34.0.0rc1 |
| 2024-01-03T20:01:28.270833+00:00 | OpenSSL Importer | Affected by | VCID-msmt-6x6r-aaaj | https://www.openssl.org/news/secadv/20200909.txt | 34.0.0rc1 |
| 2024-01-03T20:01:28.130686+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.910061+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.633549+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.293519+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:26.953413+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.677421+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.284539+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.975987+00:00 | OpenSSL Importer | Affected by | VCID-w17h-u8wd-aaaj | https://www.openssl.org/news/secadv/20220621.txt | 34.0.0rc1 |