CVE-2023-5678

Excessive time spent in DH check / generation with large Q parameter value

MEDIUM
5.3
CVSS Score
Published: November 6, 2023 at 03:47 PM UTC
Updated: October 14, 2026 at 10:17 PM UTC
7 products affected across 2 vendorsOpenSSLSIMATIC S7-1500 CPU 1518-4 Pn /dp MFP FirmwareSIMATIC S7-1500 CPU 1518F 4 Pn /dp MFP Firmware

Using OpenSSL by OpenSSL?

Get instant alerts when new vulnerabilities affect OpenSSL - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.3
Exploit prediction
EPSS 4%
SSVC
No known exploit

Description

Issue summary: Generating excessively long X9.42 DH keys or checking excessively long X9.42 DH keys or parameters may be very slow. Impact summary: Applications that use the functions DH_generate_key() to generate an X9.42 DH key may experience long delays. Likewise, applications that use DH_check_pub_key(), DH_check_pub_key_ex() or EVP_PKEY_public_check() to check an X9.42 DH key or X9.42 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. While DH_check() performs all the necessary checks (as of CVE-2023-3817), DH_check_pub_key() doesn't make any of these checks, and is therefore vulnerable for excessively large P and Q parameters. Likewise, while DH_generate_key() performs a check for an excessively large P, it doesn't check for an excessively large Q. An application that calls DH_generate_key() or DH_check_pub_key() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack. DH_generate_key() and DH_check_pub_key() are also 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_pub_key_ex(), EVP_PKEY_public_check(), and EVP_PKEY_generate(). Also vulnerable are the OpenSSL pkey command line application when using the "-pubcheck" option, as well as the OpenSSL genpkey command line application. 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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

1.0.2 ≤ v < 1.0.2zj1.1.1 ≤ v < 1.1.1x3.0.0 ≤ v < 3.0.133.1.0 ≤ v < 3.1.51.0.21.1.13.0.03.1.0
Affected range stops below 1.0.2zj, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.1.1x, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.0.13, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.1.5, so it looks safe — our inference, not a vendor statement
v < V4.0.700
Affected range stops below V4.0.700, so it looks safe — our inference, not a vendor statement
V3.1.0 ≤ v < V3.1.53.1.0
Affected range stops below V3.1.5, so it looks safe — our inference, not a vendor statement
V3.1.0 ≤ v < V3.1.53.1.0
Affected range stops below V3.1.5, so it looks safe — our inference, not a vendor statement
v < V3.0 SP1
Affected range stops below V3.0 SP1, so it looks safe — our inference, not a vendor statement
V3.1.0 ≤ v < V3.1.53.1.0
Affected range stops below V3.1.5, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.3MEDIUMCISA-ADP
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
LOW
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-606CWE-754

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card