CVE-2024-4603
Excessive time spent checking DSA keys and parameters
Reported by openssl · Published May 16, 2024
Issue summary: Checking excessively long DSA keys or parameters may be very slow. Impact summary: Applications that use the functions EVP_PKEY_param_check() or EVP_PKEY_public_check() to check a DSA public key or DSA 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 functions EVP_PKEY_param_check() or EVP_PKEY_public_check() perform various checks on DSA parameters. Some of those computations take a long time if the modulus (`p` parameter) is too large. Trying to use a very large modulus is slow and OpenSSL will not allow using public keys with a modulus which is over 10,000 bits in length for signature verification. However the key and parameter check functions do not limit the modulus size when performing the checks. An application that calls EVP_PKEY_param_check() or EVP_PKEY_public_check() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack. These functions are not called by OpenSSL itself on untrusted DSA keys so only applications that directly call these functions may be vulnerable. Also vulnerable are the OpenSSL pkey 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 affected by this issue.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| openssl | Alpine | 3.3.0-r2, 3.1.5-r0, 3.0.13-r0 |
| openssl-provider-fips | Chainguard | 3.4.0-r4 |
| openssl-provider-fips-3.1.2 | Chainguard | 3.4.0-r4 |
| openssl-devel | Amazon Linux | 1:3.0.8-1.amzn2023.0.14 |
| openssl-perl | Amazon Linux | 1:3.0.8-1.amzn2023.0.14 |
| openssl | Amazon Linux | 1:3.0.8-1.amzn2023.0.14 |
| openssl-snapsafe-libs | Amazon Linux | 1:3.0.8-1.amzn2023.0.14 |
| openssl-libs | Amazon Linux | 1:3.0.8-1.amzn2023.0.14 |
| openssl | Chainguard | 3.3.0-r8 |
| openssl | Wolfi | 3.3.0-r8 |
| openssl | openssl | 3.3.1, 3.2.2, 3.1.6, 3.0.14 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| OpenSSL | OpenSSL | 3.0.0, 3.1.0, 3.2.0 |
| alpine | openssl | 0, 0, 0 |
| openssl | openssl | 3.0.0, 3.1.0, 3.2.0 |
| chainguard | openssl-provider-fips | 0 |
| chainguard | openssl-provider-fips-3.1.2 | 0 |
| amazon:2023 | openssl-devel | 0 |
| amazon:2023 | openssl-perl | 0 |
| amazon:2023 | openssl | 0 |
| amazon:2023 | openssl-snapsafe-libs | 0 |
| OpenSSL | OpenSSL | 3.3.0, 3.0.0, 3.1.0 |
| amazon:2023 | openssl-libs | 0 |
| chainguard | openssl | 0 |
| wolfi | openssl | 0 |
Timeline
- May 16, 2024 CVE Published
- May 17, 2024 EPSS Score (30 in total, the first dated here)
- Oct 5, 2024 Coalition ESS Score (16 in total, the first dated here)
- Oct 14, 2024 CVE Updated
- Mar 17, 2026 Security Advisory (8 in total, the first dated here)
- Nov 22, 2026 Distribution Patch (4 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2024-4603
vulnetix vdb fixes CVE-2024-4603
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-4603/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- OpenSSL Advisory vendor-advisory
- 3.0.14 git commit patch
- 3.1.6 git commit patch
- 3.2.2 git commit patch
- 3.3.1 git commit patch
- http://www.openwall.com/lists/oss-security/2024/05/16/2 url
- https://security.netapp.com/advisory/ntap-20240621-0001/ url