CVE-2023-6237
Last modified
CVE-2023-6237 is a medium-severity vulnerability rated 5.9/10 on the CVSS scale. Issue summary: Checking excessively long invalid RSA public keys may take a long time. Impact summary: Applications that use the function EVP_PKEY_public_check() 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 EVP_PKEY_public_check() 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. EPSS estimates a 2.30% chance of exploitation in the next 30 days.
Description
Issue summary: Checking excessively long invalid RSA public keys may take a long time. Impact summary: Applications that use the function EVP_PKEY_public_check() 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 EVP_PKEY_public_check() 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 EVP_PKEY_public_check() and supplies an RSA key obtained from an untrusted source could be vulnerable to a Denial of Service attack. The function EVP_PKEY_public_check() 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.
Metrics
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2023-6237?
How severe is CVE-2023-6237?
How do I fix CVE-2023-6237?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2023
- CVE-2023-6231Buffer overflow in WSD probe request process of Office Multi…9.8
- CVE-2023-6232Buffer overflow in the Address Book username process in auth…9.8
- CVE-2023-6233Buffer overflow in SLP attribute request process of Office M…9.8
- CVE-2023-6234Buffer overflow in CPCA Color LUT Resource Download process …9.8
- CVE-2023-6235An uncontrolled search path element vulnerability has been f…7.8
- CVE-2023-6236A flaw was found in Red Hat Enterprise Application Platform …7.3
- CVE-2023-6238A buffer overflow vulnerability was found in the NVM Express…6.7
- CVE-2023-6239Under rare conditions, the effective permissions of an objec…8.8
- CVE-2023-6240A Marvin vulnerability side-channel leakage was found in the…6.5
- CVE-2023-6241Use After Free vulnerability in Arm Ltd Midgard GPU Kernel D…7
- CVE-2023-6242The EventON - WordPress Virtual Event Calendar Plugin plugin…4.3
- CVE-2023-6243The EventON PRO - WordPress Virtual Event Calendar Plugin pl…4.3
Are you affected by CVE-2023-6237?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
