CVE-2022-40735

What it actually does

Allows remote clients to force a server performing Diffie-Hellman key exchange to perform modular exponentiation with unnecessarily long private exponents, resulting in high CPU consumption and potential denial of service.

Why it matters to the business

Attackers can exhaust server CPU resources during TLS, SSH or IKE handshakes, leading to degraded performance or outages for services relying on Diffie-Hellman key exchange; the issue has been public for nearly four years with no official fixes listed.

How an attack unfolds

An attacker initiates a key-exchange handshake and supplies Diffie-Hellman parameters that trigger the server to use a long private exponent; repeated handshakes cause sustained high CPU load, and the flaw can be combined with CVE-2002-20001 for amplified impact.

How to fix it

Configure cryptographic libraries and servers to enforce short exponents together with appropriate subgroup constraints; disable DHE ciphersuites that permit long exponents; monitor upstream library updates for any future patches addressing exponent-size validation.

How to confirm the fix worked

Review server configuration and source code to confirm that DHE private exponents are limited to recommended bit lengths and that subgroup order validation is present; perform load testing with crafted DHE handshakes to verify CPU usage remains bounded.

Typical attack path

1. Connect to a service that negotiates DHE ciphersuites
2. Send ClientHello (TLS) or equivalent with DHE parameters lacking subgroup constraints
3. Force the server to compute modular exponentiation using a long exponent
4. Repeat the handshake at high rate to consume CPU resources
5. Optionally combine with non-public-key parameter manipulation for greater effect

How to detect it

Look in application and system logs for unusually high volumes of DHE handshakes, spikes in CPU usage during key exchange, or repeated connections from the same sources that terminate after the key-exchange phase; correlate with crypto library debug logs showing large exponent sizes.

What your security team should do

• Audit all services using DHE key exchange and disable weak ciphersuites immediately
• Implement rate limiting and connection throttling on handshake endpoints
• Add CPU and cryptographic-operation monitoring to detect anomalous load
• Track library and protocol updates for any future remediation of long-exponent handling