ALPINE-CVE-2023-3817
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.
Risk Scores
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Alpine:v3.18 | openssl | 3.1.0-r1, 3.1.0-r2, 3.1.0-r3 |
| Alpine:v3.17 | openssl | 1.1.1, 1.1.1b-r0, 1.1.1c-r0 |
| Alpine:v3.19 | openssl | 1.1.1d-r5, 1.1.1d-r4, 1.1.1d-r3 |
| Alpine:v3.21 | openssl | *, *, 0 |
| Alpine:v3.22 | openssl | 0, 3.1.1-r3, 3.1.1-r2 |
| Alpine:v3.23 | openssl | 1.1.1j-r0, 1.1.1g-r0, 1.1.1f-r0 |
| Alpine:v3.16 | openssl3 | 0, 1.1.1-r1, 1.1.1-r2 |
| Alpine:v3.20 | openssl | 1.1.1-r3, 0, 1.1.1-r0 |
| Alpine:v3.15 | openssl | 1.1.1l-r2, 0, * |
| Alpine:v3.16 | openssl | *, 0, 1.1.1l-r2 |
| Alpine:v3.15 | openssl3 | 1.1.1-r1, 1.1.1-r2, 1.1.1-r3 |
Timeline
- Jul 31, 2023 CVE Published
- Dec 3, 2025 CVE Updated
- Apr 30, 2026 Distribution Patch