Approved changes feed: RSS · Atom

cpe:2.3:a:openssl:openssl:1.0.2g:*:*:*:*:*:*:*

part: a version: 1.0.2g update: *

VendorOpenssl (1e7bcbe3-aabe-50a4-8853-ff7f6ce8bd02)
ProductOpenssl (3ac33f6d-3ea6-5807-a2fa-788d3707f5b1)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:deb/debian/openssl purl2cpe 2026-06-01 10:18:23.003507
pkg:deb/ubuntu/openssl purl2cpe 2026-06-01 10:18:23.003508
pkg:github/openssl/openssl purl2cpe 2026-06-01 10:18:23.003510
pkg:rpm/centos/openssl purl2cpe 2026-06-01 10:18:23.003511
pkg:rpm/fedora/openssl purl2cpe 2026-06-01 10:18:23.003512
pkg:rpm/opensuse/openssl purl2cpe 2026-06-01 10:18:23.003514

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2023-3817 vulnerable 2026-06-08 06:09:40.606218 Excessive time spent checking DH q parameter value
Issue summary: Checking excessively long DH keys or parameters may be very slow. Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service. The function DH_check() performs various checks on DH parameters. After fixing CVE-2023-3446 it was discovered that a large q parameter value can also trigger an overly long computation during some of these checks. A correct q value, if present, cannot be larger than the modulus p parameter, thus it is unnecessary to perform these checks if q is larger than p. An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack. The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check(). Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications when using the "-check" option. The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.
Published: 2023-07-31T15:34:13.627Z
Updated: 2025-05-05T15:53:49.014Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2017-3738 vulnerable 2026-06-08 05:09:36.160572 Details available
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.
Published: 2017-12-07T16:00:00.000Z
Updated: 2024-09-16T18:34:25.955Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2017-3737 vulnerable 2026-06-08 05:09:36.157853 Details available
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.
Published: 2017-12-07T16:00:00.000Z
Updated: 2024-09-17T03:53:31.262Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2016-6303 vulnerable 2026-06-08 05:07:59.415808 Details available
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.
Published: 2016-09-16T00:00:00.000Z
Updated: 2024-08-06T01:29:18.225Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2016-6302 vulnerable 2026-06-08 05:07:59.413822 Details available
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.
Published: 2016-09-16T00:00:00.000Z
Updated: 2024-08-06T01:29:18.217Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2016-2182 vulnerable 2026-06-08 05:07:33.539841 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2016-2181 vulnerable 2026-06-08 05:07:33.525802 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2016-2180 vulnerable 2026-06-08 05:07:33.524486 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2016-2179 vulnerable 2026-06-08 05:07:33.523200 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2016-2178 vulnerable 2026-06-08 05:07:33.521831 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2016-2177 vulnerable 2026-06-08 05:07:33.515954 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2016-2176 vulnerable 2026-06-08 05:07:33.506599 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2016-2109 vulnerable 2026-06-08 05:07:33.010320 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2016-2107 vulnerable 2026-06-08 05:07:32.998879 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2016-2106 vulnerable 2026-06-08 05:07:32.994672 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2016-2105 vulnerable 2026-06-08 05:07:32.990158 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.