Vulnerability · CVE-2024-4603
Issue summary: Checking excessively long DSA keys or parameters may be very slow.
Published May 16, 2024 · catalog updated Nov 9, 2026 · Issue summary: Checking excessively
Last checked Nov 9, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2024-4603. EPSS is 1.13%. Act only if a listed version of Issue summary: Checking excessively is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (Issue summary: Checking excessively).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-84783 · High
- CVE-2026-84782 · High
- CVE-2026-77696 · Low
- CVE-2026-75806 · Medium
- CVE-2026-75805 · Medium
- Severity
- Medium5.3
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 1.13%
- Remediation
- Version ranges on file
- Affected products
- cpe netapp/c250 firmware · cpe netapp/c400 firmware · cpe netapp/h300s firmware · cpe netapp/h500s firmware · cpe openssl/openssl
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 ( 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 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.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe netapp/c250 firmwareversion unspecified
- cpe netapp/c400 firmwareversion unspecified
- cpe netapp/h300s firmwareversion unspecified
- cpe netapp/h500s firmwareversion unspecified
- cpe openssl/openssl< 3.0.14
- cpe openssl/openssl< 3.1.6
- cpe openssl/openssl< 3.2.2
- cpe openssl/openssl< 3.3.1
How to fix CVE-2024-4603
Upgrade
CVE-2024-4603 lists a fix boundary at 3.0.14. Compare the installed build with that boundary before you change production.
Version check
Affected < 3.0.14
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2024-4603. EPSS is 1.13%. Act only if a listed version of Issue summary: Checking excessively is installed.
Which versions are affected?
Compare what you have installed with < 3.0.14, < 3.1.6, < 3.2.2, < 3.3.1. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-606; CWE-834. EPSS 1.13%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
May 16, 2024 · NIST NVD
Detected
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 functio
Nov 6, 2026 · NIST NVD
Updated
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 functio
Nov 9, 2026 · NIST NVD
Updated
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 functio
Sources
- CVE.orgVulnerability recordCVE-2024-4603
Official CVE identifier
cve.org - NIST NVDVulnerability recordCVE-2024-4603
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 parame
nvd.nist.gov
References
Freshness
Last verified in this catalog Nov 9, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- NIST NVDNov 9, 2026
- CVE.orgNov 7, 2026