Skip to content
Noroxi
CVE-2023-3446· NVD / CVE Program· CNA openssl

Excessive time spent checking DH keys and parameters

Noroxi assessment

Priority: Monitor (action score 23/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 6.5% (FIRST EPSS); higher than 93.7% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: OpenSSL OpenSSL 3.0.10, 3.1.2.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to OpenSSL OpenSSL 3.0.10, 3.1.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.3 · v3.1—No exploit Fix available
Published
Jul 19, 2023
Updated
Oct 14, 2026
EPSS
6.5% · 93th percentile

Report tools

JSON

Action score

23

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
2 / 30 · 6.5%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.3
CNA · openssl
5.3
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-3446

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
opensslopenssl

Check your server's TLS configuration

The OpenSSL version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.

Run the SSL check

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • openssl openssl1.0.2
  • openssl openssl1.1.1
  • openssl openssl3.0.0
  • openssl openssl3.1.0
  • openssl openssl3.1.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (openssl). Independent of NVD's CPE analysis and usually ahead of it.

  • OpenSSL OpenSSL

    • 3.1.0 and later · before 3.1.2affected · semver
    • 3.0.0 and later · before 3.0.10affected · semver
    • 1.1.1 and later · before 1.1.1vaffected
    • 1.0.2 and later · before 1.0.2ziaffected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8edk2-aarch64before 20220126gitbb1bba3d77-6.el8_9.320220126gitbb1bba3d77-6.el8_9.3
AlmaLinux:8edk2-ovmfbefore 20220126gitbb1bba3d77-6.el8_9.320220126gitbb1bba3d77-6.el8_9.3
AlmaLinux:8opensslbefore 1:1.1.1k-12.el8_91:1.1.1k-12.el8_9
AlmaLinux:8openssl-develbefore 1:1.1.1k-12.el8_91:1.1.1k-12.el8_9
AlmaLinux:8openssl-libsbefore 1:1.1.1k-12.el8_91:1.1.1k-12.el8_9
AlmaLinux:8openssl-perlbefore 1:1.1.1k-12.el8_91:1.1.1k-12.el8_9
AlmaLinux:9edk2-aarch64before 20231122-6.el920231122-6.el9
AlmaLinux:9edk2-ovmfbefore 20231122-6.el920231122-6.el9
AlmaLinux:9edk2-toolsbefore 20231122-6.el920231122-6.el9
AlmaLinux:9edk2-tools-docbefore 20231122-6.el920231122-6.el9
AlmaLinux:9opensslbefore 1:3.0.7-27.el91:3.0.7-27.el9
AlmaLinux:9openssl-develbefore 1:3.0.7-27.el91:3.0.7-27.el9
AlmaLinux:9openssl-libsbefore 1:3.0.7-27.el91:3.0.7-27.el9
AlmaLinux:9openssl-perlbefore 1:3.0.7-27.el91:3.0.7-27.el9
Alpine:v3.15opensslbefore 1.1.1u-r21.1.1u-r2
Alpine:v3.15openssl3before 3.0.9-r23.0.9-r2
Alpine:v3.17opensslbefore 3.0.9-r33.0.9-r3
Alpine:v3.18opensslbefore 3.1.1-r33.1.1-r3
Debian:10opensslbefore 1.1.1n-0+deb10u61.1.1n-0+deb10u6
Debian:12opensslbefore 3.0.10-1~deb12u13.0.10-1~deb12u1
Debian:13opensslbefore 3.0.10-13.0.10-1
openSUSE:Tumbleweedopenssl-1_0_0before 1.0.2u-21.11.0.2u-21.1
openSUSE:Tumbleweedopenssl-1_1before 1.1.1u-5.11.1.1u-5.1
openSUSE:Tumbleweedopenssl-3before 3.1.1-3.13.1.1-3.1

+96

Other highest-scoring records for the same primary product.

  • CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remKEV
    90Now
  • CVE-2021-3711SM2 Decryption Buffer Overflow
    65This week
  • CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code
    65This week

Published before and after this one in the same product

  • ← EarlierCVE-2023-2650May 30, 2023 · Possible DoS translating ASN.1 object identifiers
    49Plan
  • ← EarlierCVE-2023-2975Jul 14, 2023 · AES-SIV implementation ignores empty associated data entries
    21Monitor
  • Later →CVE-2023-3817Jul 31, 2023 · Excessive time spent checking DH q parameter value
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
OpenSSL OpenSSL3.0.10Vendor (CNA)
OpenSSL OpenSSL3.1.2Vendor (CNA)
almalinux:edk2-aarch6420220126gitbb1bba3d77-6.el8_9.3 · AlmaLinux:8Package registry (OSV)
almalinux:edk2-ovmf20220126gitbb1bba3d77-6.el8_9.3 · AlmaLinux:8Package registry (OSV)
almalinux:edk2-tools20231122-6.el9 · AlmaLinux:9Package registry (OSV)
almalinux:edk2-tools-doc20231122-6.el9 · AlmaLinux:9Package registry (OSV)
almalinux:openssl1:1.1.1k-12.el8_9 · AlmaLinux:8Package registry (OSV)
almalinux:openssl-devel1:1.1.1k-12.el8_9 · AlmaLinux:8Package registry (OSV)
almalinux:openssl-libs1:1.1.1k-12.el8_9 · AlmaLinux:8Package registry (OSV)
almalinux:openssl-perl1:1.1.1k-12.el8_9 · AlmaLinux:8Package registry (OSV)
alpine:openssl1.1.1u-r2 · Alpine:v3.15Package registry (OSV)
alpine:openssl33.0.9-r2 · Alpine:v3.15Package registry (OSV)
debian:openssl3.0.10-1~deb12u1 · Debian:12Package registry (OSV)
opensuse:openssl-1_0_01.0.2p-150000.3.82.1 · openSUSE:Leap 15.4Package registry (OSV)
opensuse:openssl-1_11.1.1l-150400.7.48.1 · openSUSE:Leap Micro 5.3Package registry (OSV)
opensuse:openssl-33.0.8-150500.5.8.1 · openSUSE:Leap 15.5Package registry (OSV)
red hat:jws5-tomcat0:9.0.62-19.redhat_00017.1.el7jws · Red Hat:jboss_enterprise_web_server:5.7::el7Package registry (OSV)
red hat:jws5-tomcat-admin-webapps0:9.0.62-19.redhat_00017.1.el7jws · Red Hat:jboss_enterprise_web_server:5.7::el7Package registry (OSV)
red hat:jws5-tomcat-docs-webapp0:9.0.62-19.redhat_00017.1.el7jws · Red Hat:jboss_enterprise_web_server:5.7::el7Package registry (OSV)
red hat:jws5-tomcat-el-3.0-api0:9.0.62-19.redhat_00017.1.el7jws · Red Hat:jboss_enterprise_web_server:5.7::el7Package registry (OSV)
red hat:jws5-tomcat-java-jdk110:9.0.62-19.redhat_00017.1.el7jws · Red Hat:jboss_enterprise_web_server:5.7::el7Package registry (OSV)
red hat:jws5-tomcat-java-jdk80:9.0.62-19.redhat_00017.1.el7jws · Red Hat:jboss_enterprise_web_server:5.7::el7Package registry (OSV)
red hat:jws5-tomcat-javadoc0:9.0.62-19.redhat_00017.1.el7jws · Red Hat:jboss_enterprise_web_server:5.7::el7Package registry (OSV)
red hat:jws5-tomcat-jsp-2.3-api0:9.0.62-19.redhat_00017.1.el7jws · Red Hat:jboss_enterprise_web_server:5.7::el7Package registry (OSV)
red hat:jws5-tomcat-lib0:9.0.62-19.redhat_00017.1.el7jws · Red Hat:jboss_enterprise_web_server:5.7::el7Package registry (OSV)
red hat:jws5-tomcat-native0:1.2.31-16.redhat_16.el7jws · Red Hat:jboss_enterprise_web_server:5.7::el7Package registry (OSV)
red hat:jws5-tomcat-native-debuginfo0:1.2.31-16.redhat_16.el7jws · Red Hat:jboss_enterprise_web_server:5.7::el7Package registry (OSV)
red hat:jws5-tomcat-selinux0:9.0.62-19.redhat_00017.1.el7jws · Red Hat:jboss_enterprise_web_server:5.7::el7Package registry (OSV)
rocky linux:edk20:20231122-6.el9 · Rocky Linux:9Package registry (OSV)
rocky linux:openssl1:1.1.1k-12.el8_9 · Rocky Linux:8Package registry (OSV)

+8

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days+1% in 7 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
low · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records