CVE-2024-4603: Excessive time spent checking DSA keys and parameters

Published May 16, 2024
·
Updated

Excessive time spent checking DSA keys and parameters

Other sources

Issue summary: Checking excessively long DSA keys or parameters may be very slow.

Impact summary: Applications that use the functions EVPPKEYparamcheck() or EVPPKEYpubliccheck() 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 EVPPKEYparamcheck() or EVPPKEYpubliccheck() 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 EVPPKEYparamcheck() or EVPPKEYpubliccheck() 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.

NVD

Affected Software

18 affected componentsFixes available
debian/openssl
1.1.1w-0+deb11u11.1.1n-0+deb11u53.0.14-1~deb12u13.0.14-1~deb12u23.3.2-1
IBM Concert Software<=1.0.0-1.1.0
redhat/OpenSSL<3.0.14
3.0.14
redhat/OpenSSL<3.1.6
3.1.6
redhat/OpenSSL<3.2.2
3.2.2
redhat/OpenSSL<3.3.1
3.3.1
Microsoft cbl2 hvloader 1.0.1-5
Microsoft cbl2 hvloader 1.0.1-5
Microsoft azl3 cloud-hypervisor-cvm 38.0.72-2
Microsoft cbl2 cloud-hypervisor-cvm 38.0.72-1
Microsoft azl3 openssl 3.3.0-2
Microsoft azl3 nodejs 20.10.0-2
Microsoft azl3 nodejs 20.14.0-1
Microsoft azl3 edk2 20240524git3e722403cd16-8
Microsoft azl3 openssl 3.3.2-1
Microsoft cbl2 cloud-hypervisor-cvm 38.0.72.2-1
Microsoft azl3 cloud-hypervisor-cvm 38.0.72.2-1
Microsoft cbl2 hvloader 1.0.1-6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/openssl to a version that resolves this vulnerability.

    Fixed in 1.1.1w-0+deb11u1Fixed in 1.1.1n-0+deb11u5Fixed in 3.0.14-1~deb12u1Fixed in 3.0.14-1~deb12u2Fixed in 3.3.2-1
  2. Upgrade

    Upgrade redhat/OpenSSL to a version that resolves this vulnerability.

    Fixed in 3.0.14
  3. Upgrade

    Upgrade redhat/OpenSSL to a version that resolves this vulnerability.

    Fixed in 3.1.6
  4. Upgrade

    Upgrade redhat/OpenSSL to a version that resolves this vulnerability.

    Fixed in 3.2.2
  5. Upgrade

    Upgrade redhat/OpenSSL to a version that resolves this vulnerability.

    Fixed in 3.3.1
  6. Compensating control

    For applications using EVP_PKEY_param_check() or EVP_PKEY_public_check() (including OpenSSL pkey/pkeyparam with the -check option), do not accept DSA keys/parameters from untrusted sources; only pass keys/parameters you trust into these checks to avoid DoS via long delays from excessive DSA modulus sizes.

Event History

May 16, 2024
CVE Published
via MITRE·03:21 PM
Data Sourced
via MITRE·03:21 PM
DescriptionWeakness
Data Sourced
via NVD·04:15 PM
DescriptionSeverityWeakness
May 17, 2024
Data Sourced
via Red Hat·08:13 PM
DescriptionSeverityAffected Software
May 19, 2024
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Updated
via Microsoft·07:00 AM
Description
Jul 31, 2024
Data Sourced
via Launchpad·05:31 PM
Description
Sep 13, 2024
Data Sourced
via Ubuntu·05:37 PM
RemedyDescriptionSeverityAffected Software
Aug 18, 2025
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-4603?

The severity of CVE-2024-4603 is classified as moderate due to the potential for application delays when validating excessive DSA keys or parameters.

2

How do I fix CVE-2024-4603?

To fix CVE-2024-4603, update Openssl to versions 1.1.1w-0+deb11u1, 1.1.1n-0+deb11u5, or any of the remedied versions from Red Hat.

3

What applications are affected by CVE-2024-4603?

Applications that use the functions EVP_PKEY_param_check() or EVP_PKEY_public_check() from the OpenSSL library are affected by CVE-2024-4603.

4

How can I identify if my system is vulnerable to CVE-2024-4603?

You can identify if your system is vulnerable to CVE-2024-4603 by checking if you are using OpenSSL versions prior to the patched releases mentioned in the vulnerability.

5

What are the performance implications of CVE-2024-4603?

CVE-2024-4603 may lead to significantly long delays in applications when processing very long DSA keys or parameters.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203
CVE-2024-4603 - Excessive time spent checking DSA keys and parameters - SecAlerts