CVE-2023-3817
Last modified
CVE-2023-3817 is a medium-severity vulnerability rated 5.3/10 on the CVSS scale. Issue summary: Checking excessively long DH keys or parameters may be very slow. Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH 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 function DH_check() performs various checks on DH parameters. EPSS estimates a 2.58% chance of exploitation in the next 30 days.
Description
Issue summary: Checking excessively long DH keys or parameters may be very slow. Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH 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 function DH_check() performs various checks on DH parameters. After fixing CVE-2023-3446 it was discovered that a large q parameter value can also trigger an overly long computation during some of these checks. A correct q value, if present, cannot be larger than the modulus p parameter, thus it is unnecessary to perform these checks if q is larger than p. An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack. The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check(). Also vulnerable are the OpenSSL dhparam 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 not affected by this issue.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Openssl | Openssl | >= 3.0.0, < 3.0.10 |
| Openssl | Openssl | >= 3.1.0, < 3.1.2 |
| Openssl | Openssl | 1.0.2 |
| Openssl | Openssl | 1.0.2a |
| Openssl | Openssl | 1.0.2b |
| Openssl | Openssl | 1.0.2c |
| Openssl | Openssl | 1.0.2d |
| Openssl | Openssl | 1.0.2e |
| Openssl | Openssl | 1.0.2f |
| Openssl | Openssl | 1.0.2g |
| Openssl | Openssl | 1.0.2h |
| Openssl | Openssl | 1.0.2i |
| Openssl | Openssl | 1.0.2j |
| Openssl | Openssl | 1.0.2k |
| Openssl | Openssl | 1.0.2l |
| Openssl | Openssl | 1.0.2m |
| Openssl | Openssl | 1.0.2n |
| Openssl | Openssl | 1.0.2o |
| Openssl | Openssl | 1.0.2p |
| Openssl | Openssl | 1.0.2q |
| Openssl | Openssl | 1.0.2r |
| Openssl | Openssl | 1.0.2s |
| Openssl | Openssl | 1.0.2t |
| Openssl | Openssl | 1.0.2u |
| Openssl | Openssl | 1.0.2v |
| Openssl | Openssl | 1.0.2w |
| Openssl | Openssl | 1.0.2x |
| Openssl | Openssl | 1.0.2y |
| Openssl | Openssl | 1.0.2za |
| Openssl | Openssl | 1.0.2zb |
| Openssl | Openssl | 1.0.2zc |
| Openssl | Openssl | 1.0.2zd |
| Openssl | Openssl | 1.0.2ze |
| Openssl | Openssl | 1.0.2zf |
| Openssl | Openssl | 1.0.2zg |
| Openssl | Openssl | 1.0.2zh |
| Openssl | Openssl | 1.1.1 |
| Openssl | Openssl | 1.1.1a |
| Openssl | Openssl | 1.1.1b |
| Openssl | Openssl | 1.1.1c |
| Openssl | Openssl | 1.1.1d |
| Openssl | Openssl | 1.1.1e |
| Openssl | Openssl | 1.1.1f |
| Openssl | Openssl | 1.1.1g |
| Openssl | Openssl | 1.1.1h |
| Openssl | Openssl | 1.1.1i |
| Openssl | Openssl | 1.1.1j |
| Openssl | Openssl | 1.1.1k |
| Openssl | Openssl | 1.1.1l |
| Openssl | Openssl | 1.1.1m |
Showing 50 of 58 affected configurations. See NVD for the full list.
References
- https://www.openssl.org/news/secadv/20230731.txtVendor Advisory
- https://www.openssl.org/news/secadv/20230731.txtVendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2023-3817?
How severe is CVE-2023-3817?
How do I fix CVE-2023-3817?
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-38162DHCP Server Service Denial of Service Vulnerability7.5
- CVE-2023-38163Windows Defender Attack Surface Reduction Security Feature B…7.8
- CVE-2023-38164Microsoft Dynamics 365 (on-premises) Cross-site Scripting Vu…5.4
- CVE-2023-38166Layer 2 Tunneling Protocol Remote Code Execution Vulnerabili…8.1
- CVE-2023-38167Microsoft Dynamics 365 Business Central Elevation of Privile…7.2
- CVE-2023-38169Microsoft SQL OLE DB Remote Code Execution Vulnerability8.8
- CVE-2023-38170HEVC Video Extensions Remote Code Execution Vulnerability7.8
- CVE-2023-38171Microsoft QUIC Denial of Service Vulnerability7.5
- CVE-2023-38172Microsoft Message Queuing (MSMQ) Denial of Service Vulnerabi…7.5
- CVE-2023-38173Microsoft Edge for Android Spoofing Vulnerability4.3
- CVE-2023-38174Microsoft Edge (Chromium-based) Information Disclosure Vulne…4.3
- CVE-2023-38175Microsoft Windows Defender Elevation of Privilege Vulnerabil…7.8
Are you affected by CVE-2023-3817?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
