CVE-2023-6237: Excessive time spent checking invalid RSA public keys

Published Jan 15, 2024
·
Updated

Applications that use the function EVPPKEYpubliccheck() to check RSA public keys may experience long delays. Where the key that is being checked has been obtained from an untrusted source this may lead to a Denial of Service. An application that calls EVPPKEYpubliccheck() and supplies an RSA key obtained from an untrusted source could be vulnerable to a Denial of Service attack.

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. OpenSSL versions 3.0.0 to 3.0.12, 3.1.0 to 3.1.4 and 3.2.0 are vulnerable to this issue. OpenSSL versions 1.1.1 and 1.0.2 are not affected by this issue.

References: https://www.openssl.org/news/secadv/20240115.txt https://www.openwall.com/lists/oss-security/2024/01/15/2

Upstream fix: https://github.com/openssl/openssl/commit/18c02492138d1eb8b6548cb26e7b625fb2414a2a (3.0.13) https://github.com/openssl/openssl/commit/a830f551557d3d66a84bbb18a5b889c640c36294 (3.1.5) https://github.com/openssl/openssl/commit/0b0f7abfb37350794a4b8960fafc292cd5d1b84d (3.2.1)

Other sources

Excessive time spent checking invalid RSA public keys

Microsoft

Issue summary: Checking excessively long invalid RSA public keys may take a long time.

Impact summary: Applications that use the function EVPPKEYpubliccheck() to check RSA public keys may experience long delays. Where the key that is being checked has been obtained from an untrusted source this may lead to a Denial of Service.

When function EVPPKEYpubliccheck() is called on RSA public keys, a computation is done to confirm that the RSA modulus, n, is composite. For valid RSA keys, n is a product of two or more large primes and this computation completes quickly. However, if n is an overly large prime, then this computation would take a long time.

An application that calls EVPPKEYpubliccheck() and supplies an RSA key obtained from an untrusted source could be vulnerable to a Denial of Service attack.

The function EVPPKEYpubliccheck() is not called from other OpenSSL functions however it is called from the OpenSSL pkey command line application. For that reason that application is also vulnerable if used with the '-pubin' and '-check' options on untrusted data.

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.

MITRE

OpenSSL is vulnerable to a denial of service, caused by a flaw in the handling of RSA public keys by the EVPPKEYpubliccheck() function. By persuading a victim to sue a specially crafted RSA public keys for verification, a remote attacker could exploit this vulnerability to cause long delays, and results in a denial of service condition.

IBM

Affected Software

18 affected componentsFixes available
IBM Cognos Analytics<=12.0.0-12.0.3
IBM Cognos Analytics<=11.2.0-11.2.4 FP4
debian/openssl
1.1.1w-0+deb11u11.1.1w-0+deb11u23.0.15-1~deb12u13.0.14-1~deb12u23.5.0-1
redhat/openssl<3.0.13
3.0.13
redhat/openssl<3.1.5
3.1.5
redhat/openssl<3.2.1
3.2.1
Microsoft cbl2 hvloader 1.0.1-5<1.0.1-6
1.0.1-6
Microsoft azl3 cloud-hypervisor-cvm 38.0.72-2<38.0.72.2-1
38.0.72.2-1
Microsoft azl3 openssl 3.3.0-1<3.3.0-1
3.3.0-1
Microsoft azl3 nodejs 20.14.0-1<20.14.0-1
20.14.0-1
Microsoft cbl2 nodejs18 18.20.2-1<18.20.2-1
18.20.2-1
Microsoft azl3 cloud-hypervisor-cvm 38.0.72.2-1<-
-
Microsoft cbl2 hvloader 1.0.1-6<1.0.1-6
1.0.1-6
Microsoft cbl2 cloud-hypervisor-cvm 38.0.72.2-1<-
-
Microsoft cbl2 cloud-hypervisor-cvm 38.0.72-1<38.0.72.2-1
38.0.72.2-1
Microsoft cbl2 nodejs18 18.18.2-7<18.20.2-1
18.20.2-1
Microsoft azl3 nodejs 20.10.0-2<20.14.0-1
20.14.0-1
Microsoft azl3 openssl 3.1.4-9<3.3.0-1
3.3.0-1

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.1w-0+deb11u2Fixed in 3.0.15-1~deb12u1Fixed in 3.0.14-1~deb12u2Fixed in 3.5.0-1
  2. Upgrade

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

    Fixed in 3.0.13
  3. Upgrade

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

    Fixed in 3.1.5
  4. Upgrade

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

    Fixed in 3.2.1
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.0.1-6
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 38.0.72.2-1
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.3.0-1
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 20.14.0-1
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in -
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 18.20.2-1
  11. Upgrade

    Upgrade openssl to a version that resolves this vulnerability.

    Fixed in 3.0.13Patch 18c02492138d1eb8b6548cb26e7b625fb2414a2a
  12. Upgrade

    Upgrade openssl to a version that resolves this vulnerability.

    Fixed in 3.1.5Patch a830f551557d3d66a84bbb18a5b889c640c36294
  13. Upgrade

    Upgrade openssl to a version that resolves this vulnerability.

    Fixed in 3.2.1Patch 0b0f7abfb37350794a4b8960fafc292cd5d1b84d
  14. Configuration

    Avoid running the OpenSSL pkey command line with the '-pubin' and '-check' options on untrusted RSA public key material to prevent excessive time checking invalid RSA public keys (DoS).

    OpenSSL pkey command line application -pubin and -check options usage = Do not use on untrusted data

Event History

Jan 15, 2024
Data Sourced
via Red Hat·06:04 PM
DescriptionSeverityAffected Software
Apr 25, 2024
CVE Published
via MITRE·06:27 AM
Data Sourced
via MITRE·06:27 AM
DescriptionWeakness
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
Description
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Data Sourced
via NVD·07:15 AM
DescriptionSeverityWeakness
Jun 28, 2024
Data Sourced
via Launchpad·01:33 PM
Description
Sep 16, 2024
Data Sourced
via Ubuntu·01:45 PM
RemedyDescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2023-6237?

CVE-2023-6237 has a severity level that can lead to Denial of Service (DoS) due to long delays in processing RSA public keys from untrusted sources.

2

How do I fix CVE-2023-6237?

To fix CVE-2023-6237, update your affected software to the latest patched versions provided by your vendor.

3

Which applications are affected by CVE-2023-6237?

CVE-2023-6237 affects IBM Cognos Analytics versions 12.0.0-12.0.3 and 11.2.0-11.2.4 FP4, as well as OpenSSL packages up to specific versions.

4

What functions are related to CVE-2023-6237?

CVE-2023-6237 is related to the EVP_PKEY_public_check() function used for checking RSA public keys.

5

Can untrusted RSA public keys cause problems in CVE-2023-6237?

Yes, using untrusted RSA public keys with EVP_PKEY_public_check() can lead to significant delays and potential Denial of Service.

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