Search for packages
| purl | pkg:openssl/openssl@1.0.1m |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-3d3c-x2ux-aaaa
Aliases: CVE-2015-3195 VC-OPENSSL-20151203-CVE-2015-3195 |
When presented with a malformed X509_ATTRIBUTE structure OpenSSL will leak memory. This structure is used by the PKCS#7 and CMS routines so any application which reads PKCS#7 or CMS data from untrusted sources is affected. SSL/TLS is not affected. |
Affected by 22 other vulnerabilities. Affected by 50 other vulnerabilities. |
|
VCID-42tc-p92q-aaap
Aliases: CVE-2016-2105 VC-OPENSSL-20160503-CVE-2016-2105 |
Integer overflow in the EVP_EncodeUpdate function in crypto/evp/encode.c in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h allows remote attackers to cause a denial of service (heap memory corruption) via a large amount of binary data. |
Affected by 10 other vulnerabilities. Affected by 37 other vulnerabilities. |
|
VCID-52ea-drta-aaaa
Aliases: CVE-2016-2108 VC-OPENSSL-20160503-CVE-2016-2108 |
This issue affected versions of OpenSSL prior to April 2015. The bug causing the vulnerability was fixed on April 18th 2015, and released as part of the June 11th 2015 security releases. The security impact of the bug was not known at the time. In previous versions of OpenSSL, ASN.1 encoding the value zero represented as a negative integer can cause a buffer underflow with an out-of-bounds write in i2c_ASN1_INTEGER. The ASN.1 parser does not normally create "negative zeroes" when parsing ASN.1 input, and therefore, an attacker cannot trigger this bug. However, a second, independent bug revealed that the ASN.1 parser (specifically, d2i_ASN1_TYPE) can misinterpret a large universal tag as a negative zero value. Large universal tags are not present in any common ASN.1 structures (such as X509) but are accepted as part of ANY structures. Therefore, if an application deserializes untrusted ASN.1 structures containing an ANY field, and later reserializes them, an attacker may be able to trigger an out-of-bounds write. This has been shown to cause memory corruption that is potentially exploitable with some malloc implementations. Applications that parse and re-encode X509 certificates are known to be vulnerable. Applications that verify RSA signatures on X509 certificates may also be vulnerable; however, only certificates with valid signatures trigger ASN.1 re-encoding and hence the bug. Specifically, since OpenSSL's default TLS X509 chain verification code verifies the certificate chain from root to leaf, TLS handshakes could only be targeted with valid certificates issued by trusted Certification Authorities. |
Affected by 26 other vulnerabilities. Affected by 56 other vulnerabilities. |
|
VCID-581z-anfk-aaaq
Aliases: CVE-2016-6302 VC-OPENSSL-20160823-CVE-2016-6302 |
The tls_decrypt_ticket function in ssl/t1_lib.c in OpenSSL before 1.1.0 does not consider the HMAC size during validation of the ticket length, which allows remote attackers to cause a denial of service via a ticket that is too short. |
Affected by 0 other vulnerabilities. Affected by 27 other vulnerabilities. |
|
VCID-68v4-qbae-aaak
Aliases: CVE-2015-3197 VC-OPENSSL-20160128-CVE-2015-3197 |
A malicious client can negotiate SSLv2 ciphers that have been disabled on the server and complete SSLv2 handshakes even if all SSLv2 ciphers have been disabled, provided that the SSLv2 protocol was not also disabled via SSL_OP_NO_SSLv2. |
Affected by 21 other vulnerabilities. Affected by 48 other vulnerabilities. |
|
VCID-69ax-cbdq-aaam
Aliases: CVE-2015-1791 VC-OPENSSL-20150602-CVE-2015-1791 |
If a NewSessionTicket is received by a multi-threaded client when attempting to reuse a previous ticket then a race condition can occur potentially leading to a double free of the ticket data. |
Affected by 27 other vulnerabilities. Affected by 57 other vulnerabilities. |
|
VCID-9fjn-9378-aaae
Aliases: CVE-2016-2179 VC-OPENSSL-20160822-CVE-2016-2179 |
The DTLS implementation in OpenSSL before 1.1.0 does not properly restrict the lifetime of queue entries associated with unused out-of-order messages, which allows remote attackers to cause a denial of service (memory consumption) by maintaining many crafted DTLS sessions simultaneously, related to d1_lib.c, statem_dtls.c, statem_lib.c, and statem_srvr.c. |
Affected by 0 other vulnerabilities. Affected by 27 other vulnerabilities. |
|
VCID-9wtw-93e9-aaam
Aliases: CVE-2016-0799 VC-OPENSSL-20160301-CVE-2016-0799 |
The internal |fmtstr| function used in processing a "%s" format string in the BIO_*printf functions could overflow while calculating the length of a string and cause an OOB read when printing very long strings. Additionally the internal |doapr_outch| function can attempt to write to an OOB memory location (at an offset from the NULL pointer) in the event of a memory allocation failure. In 1.0.2 and below this could be caused where the size of a buffer to be allocated is greater than INT_MAX. E.g. this could be in processing a very long "%s" format string. Memory leaks can also occur. The first issue may mask the second issue dependent on compiler behaviour. These problems could enable attacks where large amounts of untrusted data is passed to the BIO_*printf functions. If applications use these functions in this way then they could be vulnerable. OpenSSL itself uses these functions when printing out human-readable dumps of ASN.1 data. Therefore applications that print this data could be vulnerable if the data is from untrusted sources. OpenSSL command line applications could also be vulnerable where they print out ASN.1 data, or if untrusted data is passed as command line arguments. Libssl is not considered directly vulnerable. Additionally certificates etc received via remote connections via libssl are also unlikely to be able to trigger these issues because of message size limits enforced within libssl. |
Affected by 15 other vulnerabilities. Affected by 42 other vulnerabilities. |
|
VCID-a12s-yyr4-aaad
Aliases: CVE-2016-2181 VC-OPENSSL-20160819-CVE-2016-2181 |
The Anti-Replay feature in the DTLS implementation in OpenSSL before 1.1.0 mishandles early use of a new epoch number in conjunction with a large sequence number, which allows remote attackers to cause a denial of service (false-positive packet drops) via spoofed DTLS records, related to rec_layer_d1.c and ssl3_record.c. |
Affected by 0 other vulnerabilities. Affected by 27 other vulnerabilities. |
|
VCID-agz8-77e4-aaaq
Aliases: CVE-2016-2182 VC-OPENSSL-20160816-CVE-2016-2182 |
The BN_bn2dec function in crypto/bn/bn_print.c in OpenSSL before 1.1.0 does not properly validate division results, which allows remote attackers to cause a denial of service (out-of-bounds write and application crash) or possibly have unspecified other impact via unknown vectors. |
Affected by 0 other vulnerabilities. Affected by 27 other vulnerabilities. |
|
VCID-arc3-rhts-aaar
Aliases: CVE-2015-1792 VC-OPENSSL-20150611-CVE-2015-1792 |
When verifying a signedData message the CMS code can enter an infinite loop if presented with an unknown hash function OID. This can be used to perform denial of service against any system which verifies signedData messages using the CMS code. |
Affected by 27 other vulnerabilities. Affected by 57 other vulnerabilities. |
|
VCID-bms1-jrax-aaap
Aliases: CVE-2016-6304 VC-OPENSSL-20160922-CVE-2016-6304 |
Multiple memory leaks in t1_lib.c in OpenSSL before 1.0.1u, 1.0.2 before 1.0.2i, and 1.1.0 before 1.1.0a allow remote attackers to cause a denial of service (memory consumption) via large OCSP Status Request extensions. |
Affected by 0 other vulnerabilities. Affected by 27 other vulnerabilities. Affected by 22 other vulnerabilities. |
|
VCID-cg17-ah7e-aaag
Aliases: CVE-2016-2107 VC-OPENSSL-20160503-CVE-2016-2107 |
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a certain padding check, which allows remote attackers to obtain sensitive cleartext information via a padding-oracle attack against an AES CBC session. NOTE: this vulnerability exists because of an incorrect fix for CVE-2013-0169. |
Affected by 10 other vulnerabilities. Affected by 37 other vulnerabilities. |
|
VCID-eg7n-8h8z-aaaa
Aliases: CVE-2016-6306 VC-OPENSSL-20160921-CVE-2016-6306 |
The certificate parser in OpenSSL before 1.0.1u and 1.0.2 before 1.0.2i might allow remote attackers to cause a denial of service (out-of-bounds read) via crafted certificate operations, related to s3_clnt.c and s3_srvr.c. |
Affected by 0 other vulnerabilities. Affected by 27 other vulnerabilities. |
|
VCID-egbc-ecck-aaag
Aliases: CVE-2016-2109 VC-OPENSSL-20160503-CVE-2016-2109 |
The asn1_d2i_read_bio function in crypto/asn1/a_d2i_fp.c in the ASN.1 BIO implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h allows remote attackers to cause a denial of service (memory consumption) via a short invalid encoding. |
Affected by 10 other vulnerabilities. Affected by 37 other vulnerabilities. |
|
VCID-ejg3-awxf-aaan
Aliases: CVE-2016-0705 VC-OPENSSL-20160301-CVE-2016-0705 |
A double free bug was discovered when OpenSSL parses malformed DSA private keys and could lead to a DoS attack or memory corruption for applications that receive DSA private keys from untrusted sources. This scenario is considered rare. |
Affected by 15 other vulnerabilities. Affected by 42 other vulnerabilities. |
|
VCID-gp3a-7m39-aaam
Aliases: CVE-2015-3194 VC-OPENSSL-20151203-CVE-2015-3194 |
The signature verification routines will crash with a NULL pointer dereference if presented with an ASN.1 signature using the RSA PSS algorithm and absent mask generation function parameter. Since these routines are used to verify certificate signature algorithms this can be used to crash any certificate verification operation and exploited in a DoS attack. Any application which performs certificate verification is vulnerable including OpenSSL clients and servers which enable client authentication. |
Affected by 22 other vulnerabilities. Affected by 50 other vulnerabilities. |
|
VCID-gydy-46kx-aaaf
Aliases: CVE-2015-1789 VC-OPENSSL-20150611-CVE-2015-1789 |
X509_cmp_time does not properly check the length of the ASN1_TIME string and can read a few bytes out of bounds. In addition, X509_cmp_time accepts an arbitrary number of fractional seconds in the time string. An attacker can use this to craft malformed certificates and CRLs of various sizes and potentially cause a segmentation fault, resulting in a DoS on applications that verify certificates or CRLs. TLS clients that verify CRLs are affected. TLS clients and servers with client authentication enabled may be affected if they use custom verification callbacks. |
Affected by 27 other vulnerabilities. Affected by 57 other vulnerabilities. |
|
VCID-hzh3-5uc4-aaap
Aliases: CVE-2015-3196 VC-OPENSSL-20151203-CVE-2015-3196 |
If PSK identity hints are received by a multi-threaded client then the values are wrongly updated in the parent SSL_CTX structure. This can result in a race condition potentially leading to a double free of the identify hint data. |
Affected by 24 other vulnerabilities. Affected by 54 other vulnerabilities. |
|
VCID-kryh-pfgh-aaag
Aliases: CVE-2016-2177 VC-OPENSSL-20160601-CVE-2016-2177 |
OpenSSL through 1.0.2h incorrectly uses pointer arithmetic for heap-buffer boundary checks, which might allow remote attackers to cause a denial of service (integer overflow and application crash) or possibly have unspecified other impact by leveraging unexpected malloc behavior, related to s3_srvr.c, ssl_sess.c, and t1_lib.c. |
Affected by 0 other vulnerabilities. Affected by 27 other vulnerabilities. |
|
VCID-m4nz-uw2e-aaaq
Aliases: CVE-2016-0798 VC-OPENSSL-20160301-CVE-2016-0798 |
The SRP user database lookup method SRP_VBASE_get_by_user had confusing memory management semantics; the returned pointer was sometimes newly allocated, and sometimes owned by the callee. The calling code has no way of distinguishing these two cases. Specifically, SRP servers that configure a secret seed to hide valid login information are vulnerable to a memory leak: an attacker connecting with an invalid username can cause a memory leak of around 300 bytes per connection. Servers that do not configure SRP, or configure SRP but do not configure a seed are not vulnerable. In Apache, the seed directive is known as SSLSRPUnknownUserSeed. To mitigate the memory leak, the seed handling in SRP_VBASE_get_by_user is now disabled even if the user has configured a seed. Applications are advised to migrate to SRP_VBASE_get1_by_user. However, note that OpenSSL makes no strong guarantees about the indistinguishability of valid and invalid logins. In particular, computations are currently not carried out in constant time. |
Affected by 15 other vulnerabilities. Affected by 42 other vulnerabilities. |
|
VCID-rhab-a2ya-aaae
Aliases: CVE-2015-1788 VC-OPENSSL-20150611-CVE-2015-1788 |
When processing an ECParameters structure OpenSSL enters an infinite loop if the curve specified is over a specially malformed binary polynomial field. This can be used to perform denial of service against any system which processes public keys, certificate requests or certificates. This includes TLS clients and TLS servers with client authentication enabled. |
Affected by 27 other vulnerabilities. Affected by 57 other vulnerabilities. |
|
VCID-sgbg-ntsk-aaac
Aliases: CVE-2016-6303 VC-OPENSSL-20160824-CVE-2016-6303 |
Integer overflow in the MDC2_Update function in crypto/mdc2/mdc2dgst.c in OpenSSL before 1.1.0 allows remote attackers to cause a denial of service (out-of-bounds write and application crash) or possibly have unspecified other impact via unknown vectors. |
Affected by 0 other vulnerabilities. Affected by 27 other vulnerabilities. |
|
VCID-t9zu-eqq1-aaag
Aliases: CVE-2016-0702 VC-OPENSSL-20160301-CVE-2016-0702 |
A side-channel attack was found which makes use of cache-bank conflicts on the Intel Sandy-Bridge microarchitecture which could lead to the recovery of RSA keys. The ability to exploit this issue is limited as it relies on an attacker who has control of code in a thread running on the same hyper-threaded core as the victim thread which is performing decryptions. |
Affected by 15 other vulnerabilities. Affected by 42 other vulnerabilities. |
|
VCID-tc8g-det5-aaad
Aliases: CVE-2015-1790 VC-OPENSSL-20150611-CVE-2015-1790 |
The PKCS#7 parsing code does not handle missing inner EncryptedContent correctly. An attacker can craft malformed ASN.1-encoded PKCS#7 blobs with missing content and trigger a NULL pointer dereference on parsing. Applications that decrypt PKCS#7 data or otherwise parse PKCS#7 structures from untrusted sources are affected. OpenSSL clients and servers are not affected. |
Affected by 27 other vulnerabilities. Affected by 57 other vulnerabilities. |
|
VCID-ue1t-xset-aaah
Aliases: CVE-2016-2180 VC-OPENSSL-20160722-CVE-2016-2180 |
The TS_OBJ_print_bio function in crypto/ts/ts_lib.c in the X.509 Public Key Infrastructure Time-Stamp Protocol (TSP) implementation in OpenSSL through 1.0.2h allows remote attackers to cause a denial of service (out-of-bounds read and application crash) via a crafted time-stamp file that is mishandled by the "openssl ts" command. |
Affected by 0 other vulnerabilities. Affected by 27 other vulnerabilities. |
|
VCID-uh6s-bvxe-aaaf
Aliases: CVE-2016-0797 VC-OPENSSL-20160301-CVE-2016-0797 |
In the BN_hex2bn function the number of hex digits is calculated using an int value |i|. Later |bn_expand| is called with a value of |i * 4|. For large values of |i| this can result in |bn_expand| not allocating any memory because |i * 4| is negative. This can leave the internal BIGNUM data field as NULL leading to a subsequent NULL ptr deref. For very large values of |i|, the calculation |i * 4| could be a positive value smaller than |i|. In this case memory is allocated to the internal BIGNUM data field, but it is insufficiently sized leading to heap corruption. A similar issue exists in BN_dec2bn. This could have security consequences if BN_hex2bn/BN_dec2bn is ever called by user applications with very large untrusted hex/dec data. This is anticipated to be a rare occurrence. All OpenSSL internal usage of these functions use data that is not expected to be untrusted, e.g. config file data or application command line arguments. If user developed applications generate config file data based on untrusted data then it is possible that this could also lead to security consequences. This is also anticipated to be rare. |
Affected by 15 other vulnerabilities. Affected by 42 other vulnerabilities. |
|
VCID-vz46-gfhm-aaap
Aliases: CVE-2016-0800 VC-OPENSSL-20160301-CVE-2016-0800 |
A cross-protocol attack was discovered that could lead to decryption of TLS sessions by using a server supporting SSLv2 and EXPORT cipher suites as a Bleichenbacher RSA padding oracle. Note that traffic between clients and non-vulnerable servers can be decrypted provided another server supporting SSLv2 and EXPORT ciphers (even with a different protocol such as SMTP, IMAP or POP) shares the RSA keys of the non-vulnerable server. This vulnerability is known as DROWN (CVE-2016-0800). Recovering one session key requires the attacker to perform approximately 2^50 computation, as well as thousands of connections to the affected server. A more efficient variant of the DROWN attack exists against unpatched OpenSSL servers using versions that predate 1.0.2a, 1.0.1m, 1.0.0r and 0.9.8zf released on 19/Mar/2015 (see CVE-2016-0703 below). Users can avoid this issue by disabling the SSLv2 protocol in all their SSL/TLS servers, if they've not done so already. Disabling all SSLv2 ciphers is also sufficient, provided the patches for CVE-2015-3197 (fixed in OpenSSL 1.0.1r and 1.0.2f) have been deployed. Servers that have not disabled the SSLv2 protocol, and are not patched for CVE-2015-3197 are vulnerable to DROWN even if all SSLv2 ciphers are nominally disabled, because malicious clients can force the use of SSLv2 with EXPORT ciphers. OpenSSL 1.0.2g and 1.0.1s deploy the following mitigation against DROWN: SSLv2 is now by default disabled at build-time. Builds that are not configured with "enable-ssl2" will not support SSLv2. Even if "enable-ssl2" is used, users who want to negotiate SSLv2 via the version-flexible SSLv23_method() will need to explicitly call either of: SSL_CTX_clear_options(ctx, SSL_OP_NO_SSLv2); or SSL_clear_options(ssl, SSL_OP_NO_SSLv2); as appropriate. Even if either of those is used, or the application explicitly uses the version-specific SSLv2_method() or its client or server variants, SSLv2 ciphers vulnerable to exhaustive search key recovery have been removed. Specifically, the SSLv2 40-bit EXPORT ciphers, and SSLv2 56-bit DES are no longer available. In addition, weak ciphers in SSLv3 and up are now disabled in default builds of OpenSSL. Builds that are not configured with "enable-weak-ssl-ciphers" will not provide any "EXPORT" or "LOW" strength ciphers. |
Affected by 15 other vulnerabilities. Affected by 42 other vulnerabilities. |
|
VCID-wdvv-5wyx-aaaa
Aliases: CVE-2016-2176 VC-OPENSSL-20160503-CVE-2016-2176 |
The X509_NAME_oneline function in crypto/x509/x509_obj.c in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h allows remote attackers to obtain sensitive information from process stack memory or cause a denial of service (buffer over-read) via crafted EBCDIC ASN.1 data. |
Affected by 10 other vulnerabilities. Affected by 37 other vulnerabilities. |
|
VCID-xsy7-be4x-aaas
Aliases: CVE-2016-2106 VC-OPENSSL-20160503-CVE-2016-2106 |
Integer overflow in the EVP_EncryptUpdate function in crypto/evp/evp_enc.c in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h allows remote attackers to cause a denial of service (heap memory corruption) via a large amount of data. |
Affected by 10 other vulnerabilities. Affected by 37 other vulnerabilities. |
|
VCID-z6bg-hyhu-aaas
Aliases: CVE-2016-2178 VC-OPENSSL-20160607-CVE-2016-2178 |
The dsa_sign_setup function in crypto/dsa/dsa_ossl.c in OpenSSL through 1.0.2h does not properly ensure the use of constant-time operations, which makes it easier for local users to discover a DSA private key via a timing side-channel attack. |
Affected by 0 other vulnerabilities. Affected by 27 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-1pke-t171-aaas | ASN.1 structure reuse memory corruption. Reusing a structure in ASN.1 parsing may allow an attacker to cause memory corruption via an invalid write. Such reuse is and has been strongly discouraged and is believed to be rare. |
CVE-2015-0287
VC-OPENSSL-20150319-CVE-2015-0287 |
| VCID-1t6y-1zjy-aaae | This issue only affected versions of OpenSSL prior to March 19th 2015 at which time the code was refactored to address the vulnerability CVE-2015-0293. s2_srvr.c overwrite the wrong bytes in the master-key when applying Bleichenbacher protection for export cipher suites. This provides a Bleichenbacher oracle, and could potentially allow more efficient variants of the DROWN attack. |
CVE-2016-0704
VC-OPENSSL-20160301-CVE-2016-0704 |
| VCID-75pz-sunt-aaaa | Use After Free following d2i_ECPrivatekey error. A malformed EC private key file consumed via the d2i_ECPrivateKey function could cause a use after free condition. This, in turn, could cause a double free in several private key parsing functions (such as d2i_PrivateKey or EVP_PKCS82PKEY) and could lead to a DoS attack or memory corruption for applications that receive EC private keys from untrusted sources. This scenario is considered rare. |
CVE-2015-0209
VC-OPENSSL-20150319-CVE-2015-0209 |
| VCID-914k-6fj2-aaac | Segmentation fault in ASN1_TYPE_cmp. The function ASN1_TYPE_cmp will crash with an invalid read if an attempt is made to compare ASN.1 boolean types. Since ASN1_TYPE_cmp is used to check certificate signature algorithm consistency this can be used to crash any certificate verification operation and exploited in a DoS attack. Any application which performs certificate verification is vulnerable including OpenSSL clients and servers which enable client authentication. |
CVE-2015-0286
VC-OPENSSL-20150319-CVE-2015-0286 |
| VCID-9few-spp9-aaag | DoS via reachable assert in SSLv2 servers. A malicious client can trigger an OPENSSL_assert in servers that both support SSLv2 and enable export cipher suites by sending a specially crafted SSLv2 CLIENT-MASTER-KEY message. |
CVE-2015-0293
VC-OPENSSL-20150319-CVE-2015-0293 |
| VCID-bsap-s527-aaaj | PKCS#7 NULL pointer dereference. The PKCS#7 parsing code does not handle missing outer ContentInfo correctly. An attacker can craft malformed ASN.1-encoded PKCS#7 blobs with missing content and trigger a NULL pointer dereference on parsing. Applications that verify PKCS#7 signatures, decrypt PKCS#7 data or otherwise parse PKCS#7 structures from untrusted sources are affected. OpenSSL clients and servers are not affected. |
CVE-2015-0289
VC-OPENSSL-20150319-CVE-2015-0289 |
| VCID-ftte-av19-aaad | This issue only affected versions of OpenSSL prior to March 19th 2015 at which time the code was refactored to address vulnerability CVE-2015-0293. s2_srvr.c did not enforce that clear-key-length is 0 for non-export ciphers. If clear-key bytes are present for these ciphers, they *displace* encrypted-key bytes. This leads to an efficient divide-and-conquer key recovery attack: if an eavesdropper has intercepted an SSLv2 handshake, they can use the server as an oracle to determine the SSLv2 master-key, using only 16 connections to the server and negligible computation. More importantly, this leads to a more efficient version of DROWN that is effective against non-export ciphersuites, and requires no significant computation. |
CVE-2016-0703
VC-OPENSSL-20160301-CVE-2016-0703 |
| VCID-y49b-wcn4-aaaa | X509_to_X509_REQ NULL pointer deref. The function X509_to_X509_REQ will crash with a NULL pointer dereference if the certificate key is invalid. This function is rarely used in practice. |
CVE-2015-0288
VC-OPENSSL-20150302-CVE-2015-0288 |
| Date | Actor | Action | Vulnerability | Source | VulnerableCode Version |
|---|---|---|---|---|---|
| 2024-01-03T20:01:42.298555+00:00 | OpenSSL Importer | Fixing | VCID-y49b-wcn4-aaaa | https://www.openssl.org/news/secadv/20150319.txt | 34.0.0rc1 |
| 2024-01-03T20:01:41.917744+00:00 | OpenSSL Importer | Fixing | VCID-75pz-sunt-aaaa | https://www.openssl.org/news/secadv/20150319.txt | 34.0.0rc1 |
| 2024-01-03T20:01:41.503011+00:00 | OpenSSL Importer | Fixing | VCID-9few-spp9-aaag | https://www.openssl.org/news/secadv/20150319.txt | 34.0.0rc1 |
| 2024-01-03T20:01:40.870132+00:00 | OpenSSL Importer | Fixing | VCID-bsap-s527-aaaj | https://www.openssl.org/news/secadv/20150319.txt | 34.0.0rc1 |
| 2024-01-03T20:01:40.495204+00:00 | OpenSSL Importer | Fixing | VCID-1pke-t171-aaas | https://www.openssl.org/news/secadv/20150319.txt | 34.0.0rc1 |
| 2024-01-03T20:01:40.084021+00:00 | OpenSSL Importer | Fixing | VCID-914k-6fj2-aaac | https://www.openssl.org/news/secadv/20150319.txt | 34.0.0rc1 |
| 2024-01-03T20:01:39.493651+00:00 | OpenSSL Importer | Affected by | VCID-69ax-cbdq-aaam | https://www.openssl.org/news/secadv/20150611.txt | 34.0.0rc1 |
| 2024-01-03T20:01:39.094212+00:00 | OpenSSL Importer | Affected by | VCID-arc3-rhts-aaar | https://www.openssl.org/news/secadv/20150611.txt | 34.0.0rc1 |
| 2024-01-03T20:01:38.701277+00:00 | OpenSSL Importer | Affected by | VCID-tc8g-det5-aaad | https://www.openssl.org/news/secadv/20150611.txt | 34.0.0rc1 |
| 2024-01-03T20:01:38.315126+00:00 | OpenSSL Importer | Affected by | VCID-gydy-46kx-aaaf | https://www.openssl.org/news/secadv/20150611.txt | 34.0.0rc1 |
| 2024-01-03T20:01:37.928368+00:00 | OpenSSL Importer | Affected by | VCID-rhab-a2ya-aaae | https://www.openssl.org/news/secadv/20150611.txt | 34.0.0rc1 |
| 2024-01-03T20:01:37.585653+00:00 | OpenSSL Importer | Affected by | VCID-hzh3-5uc4-aaap | https://www.openssl.org/news/secadv/20151203.txt | 34.0.0rc1 |
| 2024-01-03T20:01:37.328306+00:00 | OpenSSL Importer | Affected by | VCID-3d3c-x2ux-aaaa | https://www.openssl.org/news/secadv/20151203.txt | 34.0.0rc1 |
| 2024-01-03T20:01:36.891755+00:00 | OpenSSL Importer | Affected by | VCID-gp3a-7m39-aaam | https://www.openssl.org/news/secadv/20151203.txt | 34.0.0rc1 |
| 2024-01-03T20:01:36.659491+00:00 | OpenSSL Importer | Affected by | VCID-68v4-qbae-aaak | https://www.openssl.org/news/secadv/20160128.txt | 34.0.0rc1 |
| 2024-01-03T20:01:36.511126+00:00 | OpenSSL Importer | Fixing | VCID-1t6y-1zjy-aaae | https://www.openssl.org/news/secadv/20160301.txt | 34.0.0rc1 |
| 2024-01-03T20:01:36.138507+00:00 | OpenSSL Importer | Fixing | VCID-ftte-av19-aaad | https://www.openssl.org/news/secadv/20160301.txt | 34.0.0rc1 |
| 2024-01-03T20:01:35.690870+00:00 | OpenSSL Importer | Affected by | VCID-t9zu-eqq1-aaag | https://www.openssl.org/news/secadv/20160301.txt | 34.0.0rc1 |
| 2024-01-03T20:01:35.514701+00:00 | OpenSSL Importer | Affected by | VCID-9wtw-93e9-aaam | https://www.openssl.org/news/secadv/20160301.txt | 34.0.0rc1 |
| 2024-01-03T20:01:35.352867+00:00 | OpenSSL Importer | Affected by | VCID-uh6s-bvxe-aaaf | https://www.openssl.org/news/secadv/20160301.txt | 34.0.0rc1 |
| 2024-01-03T20:01:35.178556+00:00 | OpenSSL Importer | Affected by | VCID-m4nz-uw2e-aaaq | https://www.openssl.org/news/secadv/20160301.txt | 34.0.0rc1 |
| 2024-01-03T20:01:35.014871+00:00 | OpenSSL Importer | Affected by | VCID-ejg3-awxf-aaan | https://www.openssl.org/news/secadv/20160301.txt | 34.0.0rc1 |
| 2024-01-03T20:01:34.837363+00:00 | OpenSSL Importer | Affected by | VCID-vz46-gfhm-aaap | https://www.openssl.org/news/secadv/20160301.txt | 34.0.0rc1 |
| 2024-01-03T20:01:34.659528+00:00 | OpenSSL Importer | Affected by | VCID-wdvv-5wyx-aaaa | https://www.openssl.org/news/secadv/20160503.txt | 34.0.0rc1 |
| 2024-01-03T20:01:34.490641+00:00 | OpenSSL Importer | Affected by | VCID-egbc-ecck-aaag | https://www.openssl.org/news/secadv/20160503.txt | 34.0.0rc1 |
| 2024-01-03T20:01:34.319152+00:00 | OpenSSL Importer | Affected by | VCID-xsy7-be4x-aaas | https://www.openssl.org/news/secadv/20160503.txt | 34.0.0rc1 |
| 2024-01-03T20:01:34.147589+00:00 | OpenSSL Importer | Affected by | VCID-42tc-p92q-aaap | https://www.openssl.org/news/secadv/20160503.txt | 34.0.0rc1 |
| 2024-01-03T20:01:33.975210+00:00 | OpenSSL Importer | Affected by | VCID-cg17-ah7e-aaag | https://www.openssl.org/news/secadv/20160503.txt | 34.0.0rc1 |
| 2024-01-03T20:01:33.849721+00:00 | OpenSSL Importer | Affected by | VCID-52ea-drta-aaaa | https://www.openssl.org/news/secadv/20160503.txt | 34.0.0rc1 |
| 2024-01-03T20:01:33.611856+00:00 | OpenSSL Importer | Affected by | VCID-eg7n-8h8z-aaaa | https://www.openssl.org/news/secadv/20160922.txt | 34.0.0rc1 |
| 2024-01-03T20:01:33.418899+00:00 | OpenSSL Importer | Affected by | VCID-a12s-yyr4-aaad | https://www.openssl.org/news/secadv/20160922.txt | 34.0.0rc1 |
| 2024-01-03T20:01:33.226894+00:00 | OpenSSL Importer | Affected by | VCID-9fjn-9378-aaae | https://www.openssl.org/news/secadv/20160922.txt | 34.0.0rc1 |
| 2024-01-03T20:01:33.040339+00:00 | OpenSSL Importer | Affected by | VCID-z6bg-hyhu-aaas | https://www.openssl.org/news/secadv/20160922.txt | 34.0.0rc1 |
| 2024-01-03T20:01:32.853821+00:00 | OpenSSL Importer | Affected by | VCID-kryh-pfgh-aaag | https://www.openssl.org/news/secadv/20160922.txt | 34.0.0rc1 |
| 2024-01-03T20:01:32.667768+00:00 | OpenSSL Importer | Affected by | VCID-ue1t-xset-aaah | https://www.openssl.org/news/secadv/20160922.txt | 34.0.0rc1 |
| 2024-01-03T20:01:32.483889+00:00 | OpenSSL Importer | Affected by | VCID-agz8-77e4-aaaq | https://www.openssl.org/news/secadv/20160922.txt | 34.0.0rc1 |
| 2024-01-03T20:01:32.299984+00:00 | OpenSSL Importer | Affected by | VCID-581z-anfk-aaaq | https://www.openssl.org/news/secadv/20160922.txt | 34.0.0rc1 |
| 2024-01-03T20:01:32.108649+00:00 | OpenSSL Importer | Affected by | VCID-sgbg-ntsk-aaac | https://www.openssl.org/news/secadv/20160922.txt | 34.0.0rc1 |
| 2024-01-03T20:01:31.847236+00:00 | OpenSSL Importer | Affected by | VCID-bms1-jrax-aaap | https://www.openssl.org/news/secadv/20160922.txt | 34.0.0rc1 |