CVE-2023-3446

MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2023-07-19. NVD baseline CVSS 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 6%CVSS: 5.3Exploit: NoneExposed: 0

A fix is available — apply it.

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. One of those checks confirms that the modulus ('p' parameter) is not too large. Trying to use a very large modulus is slow and OpenSSL will not normally use a modulus which is over 10,000 bits in length.

However the DH_check() function checks numerous aspects of the key or parameters that have been supplied. Some of those checks use the supplied modulus value even if it has already been found to be too large.

An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulernable 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.

CVSS v3
5.3
EG Score
5.3(medium)
EPSS
91.9%
KEV
Not listed

Published

July 19, 2023

Last Modified

April 23, 2025

References (18)

Patch Availability(17)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenssl (1.0.2g-1ubuntu4.20+esm10) @ xenial2026-05-24ubuntu
ubuntuqemu-efi-riscv64 (2025.02-3ubuntu2.2) @ plucky2026-05-24ubuntu
ubuntuopenssl (3.0.10-1ubuntu2.1) @ mantic2026-05-24ubuntu
ubuntuopenssl (1.1.1f-1ubuntu2.20) @ focal2026-05-24ubuntu
ubuntuopenssl1.0 (1.0.2n-1ubuntu5.13+esm1) @ bionic2026-05-24ubuntu
ubuntuopenssl (1.0.1f-1ubuntu2.27+esm10) @ trusty2026-05-24ubuntu
redhatopenssl-1:3.0.7-27.el92024-04-30redhat
redhatedk2-0:20231122-6.el92024-04-30redhat
redhatedk2-0:20220126gitbb1bba3d77-4.el8_8.32024-03-19redhat
redhatedk2-0:20220126gitbb1bba3d77-6.el8_9.32024-02-20redhat
redhatedk2-0:20220126gitbb1bba3d77-2.el8_6.22024-01-25redhat
redhatopenssl-1:1.1.1k-12.el8_62024-01-11redhat
redhatopenssl-1:1.1.1k-12.el8_82024-01-10redhat
redhatopenssl-1:1.1.1k-12.el8_92023-12-19redhat
redhatjbcs-httpd24-openssl-1:1.1.1k-16.el7jbcs2023-12-07redhat
redhatopenssl2023-12-07redhat
redhatjws5-tomcat-native-0:1.2.31-16.redhat_16.el9jws2023-12-07redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(14)

Data Freshness Timeline

(refreshed 9× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:26 UTCEPSS rescore
  2. 2026-07-11 08:26 UTCEPSS rescore
  3. 2026-07-09 19:08 UTCEPSS rescore
  4. 2026-07-08 15:13 UTCEPSS rescore
  5. 2026-07-07 13:44 UTCEPSS rescore
  6. 2026-07-06 16:26 UTCEPSS rescore
  7. 2026-07-06 16:26 UTCEPSS rescore
  8. 2026-07-06 02:22 UTCEPSS rescore
  9. 2026-07-05 02:29 UTCEPSS rescore
  10. 2026-07-04 06:29 UTCEPSS rescore
  11. 2026-07-01 15:05 UTCEPSS rescore
  12. 2026-06-30 23:21 UTCEPSS rescore
  13. 2026-06-30 23:21 UTCEPSS rescore
  14. 2026-06-29 14:05 UTCEPSS rescore
  15. 2026-06-28 04:55 UTCEPSS rescore
  16. 2026-06-28 04:55 UTCEPSS rescore
  17. 2026-06-27 15:04 UTCOSV refresh
  18. 2026-06-27 03:07 UTCEPSS rescore
  19. 2026-06-27 03:07 UTCEPSS rescore
  20. 2026-06-25 13:48 UTCEPSS rescore
  21. 2026-06-25 13:48 UTCEPSS rescore
  22. 2026-06-24 14:04 UTCEPSS rescore
  23. 2026-06-24 14:04 UTCEPSS rescore
  24. 2026-06-23 21:31 UTCEPSS rescore
  25. 2026-06-23 21:31 UTCEPSS rescore
Show 57 more
  1. 2026-06-21 14:55 UTCEPSS rescore
  2. 2026-06-21 14:55 UTCEPSS rescore
  3. 2026-06-21 01:58 UTCEPSS rescore
  4. 2026-06-21 01:58 UTCEPSS rescore
  5. 2026-06-18 17:51 UTCEPSS rescore
  6. 2026-06-17 17:51 UTCEPSS rescore
  7. 2026-06-17 17:51 UTCEPSS rescore
  8. 2026-06-16 17:51 UTCEPSS rescore
  9. 2026-06-16 17:51 UTCEPSS rescore
  10. 2026-06-15 17:47 UTCEPSS rescore
  11. 2026-06-15 17:47 UTCEPSS rescore
  12. 2026-06-14 23:16 UTCEPSS rescore
  13. 2026-06-13 22:59 UTCEPSS rescore
  14. 2026-06-13 22:59 UTCEPSS rescore
  15. 2026-06-12 23:10 UTCEPSS rescore
  16. 2026-06-12 23:10 UTCEPSS rescore
  17. 2026-06-11 13:59 UTCEPSS rescore
  18. 2026-06-11 13:59 UTCEPSS rescore
  19. 2026-06-10 22:17 UTCEPSS rescore
  20. 2026-06-10 13:21 UTCEPSS rescore
  21. 2026-06-10 13:21 UTCEPSS rescore
  22. 2026-06-10 01:47 UTCOSV refresh
  23. 2026-06-08 14:16 UTCEPSS rescore
  24. 2026-06-08 14:16 UTCEPSS rescore
  25. 2026-06-07 15:23 UTCEPSS rescore
  26. 2026-06-07 15:23 UTCEPSS rescore
  27. 2026-06-06 13:46 UTCEPSS rescore
  28. 2026-06-06 13:46 UTCEPSS rescore
  29. 2026-06-05 22:46 UTCEPSS rescore
  30. 2026-06-05 22:46 UTCEPSS rescore
  31. 2026-06-05 06:09 UTCEPSS rescore
  32. 2026-06-05 06:09 UTCEPSS rescore
  33. 2026-06-05 06:09 UTCEPSS rescore
  34. 2026-06-04 13:11 UTCEPSS rescore
  35. 2026-06-04 13:11 UTCEPSS rescore
  36. 2026-06-02 20:12 UTCEPSS rescore
  37. 2026-06-02 20:12 UTCEPSS rescore
  38. 2026-06-01 13:51 UTCEPSS rescore
  39. 2026-06-01 13:51 UTCEPSS rescore
  40. 2026-05-31 22:30 UTCEPSS rescore
  41. 2026-05-31 22:29 UTCEPSS rescore
  42. 2026-05-31 00:15 UTCEPSS rescore
  43. 2026-05-31 00:15 UTCEPSS rescore
  44. 2026-05-29 13:43 UTCEPSS rescore
  45. 2026-05-29 13:43 UTCEPSS rescore
  46. 2026-05-28 13:44 UTCEPSS rescore
  47. 2026-05-28 13:43 UTCEPSS rescore
  48. 2026-05-27 13:39 UTCEPSS rescore
  49. 2026-05-27 13:39 UTCEPSS rescore
  50. 2026-05-26 13:43 UTCEPSS rescore
  51. 2026-05-26 13:43 UTCEPSS rescore
  52. 2026-05-26 07:18 UTCEPSS rescore
  53. 2026-05-26 07:18 UTCEPSS rescore
  54. 2026-05-26 07:18 UTCEPSS rescore
  55. 2026-05-24 20:54 UTCEG score recompute
  56. 2026-05-24 20:54 UTCVendor advisory
  57. 2026-05-24 20:54 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2023-3446?
CVE-2023-3446 is a medium vulnerability published on July 19, 2023. Issue summary: Checking excessively long DH keys or parameters may be very slow. Impact summary: Applications that use the functions DHcheck(), DHcheck_ex() or EVPPKEYparam_check() to check a DH key or DH parameters may experience long delays. Where the key or parameters that are being checked have…
When was CVE-2023-3446 disclosed?
CVE-2023-3446 was first published in the National Vulnerability Database on July 19, 2023, with the most recent update on April 23, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-3446 actively exploited?
CVE-2023-3446 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 91.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-3446?
CVE-2023-3446 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2023-3446?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-3446, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-3446

Explore →

Is Your Infrastructure Affected by CVE-2023-3446?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.