CVE-2026-84897 wolfSSH server accepts server-to-client DH group exchange messages from an unauthenticated client, causing pre-authentication primality-test CPU exhaustion and key exchange role confusion
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- No known exploitation · automatable: yes · technical impact: partial
Description
src/internal.c in wolfSSL wolfSSH through 1.5.0 admits the server-to-client Diffie-Hellman group exchange messages SSH_MSG_KEX_DH_GEX_GROUP (31) and SSH_MSG_KEX_DH_GEX_REPLY (33) when a server receives them from an unauthenticated client. IsMessageAllowedServer() applies no direction check to the key exchange message range: when the peer is keying and no particular message is expected, which is the state a server is in for the whole window after it processes the client's KEXINIT because nothing sets handshake->expectMsgId there, the function falls out of its expectation branch without a verdict and reaches a numeric bound that admits every message id from 30 through 34. A client that negotiates diffie-hellman-group-exchange-sha256 and then sends message 31 makes the server run the client-side handler DoKexDhGexGroup(), which validates the attacker-supplied group with two 8-round Miller-Rabin primality tests, one on p and one on (p-1)/2, on a value of up to 8192 bits. The handler then returns success: the server stores the attacker's prime and generator, generates a Diffie-Hellman key pair in the attacker's group, and sends the client-role message SSH_MSG_KEX_DH_GEX_INIT (32) back to the attacker. Published RFC 3526 safe primes are the worst-case input and cost the attacker nothing to obtain. The primality validation was added in 1.5.0; versions from 1.2.0 through 1.4.22 admit the same message and enter the same client-role path without the primality cost. Message 33 is admitted as well, but on a server it is rejected before any cryptography because no public key check callback is registered, so it carries no comparable cost. Builds that define WOLFSSH_NO_DH_GEX_SHA256, which is implied by WOLFSSH_NO_DH or NO_SHA256, are unaffected.
Upgrade path
3 packages: 3 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| alpine/wolfssh(Alpine v3.24) | >= 1.2.0, < 1.6.0-r0 | 1.6.0-r0 | Fixed |
| wolfSSH | >= 1.2.0, < 1.6.0 | 1.6.0 | Fixed |
| wolfSSL wolfSSH | >= 1.2.0, < 1.6.0 | 1.6.0 | Fixed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| wolfSSL wolfSSH | >= 1.2.0, < 1.6.0 | 1.6.0 |
| alpine/wolfssh(Alpine:v3.24) | >= 1.2.0, < 1.6.0-r0 | 1.6.0-r0 |
| wolfSSH | >= 1.2.0, < 1.6.0 | 1.6.0 |
References
- Fix PR #1221 patch
- Fix commit a472f1ee (reject the KEX replies a server never receives) patch
- RFC 4419 sections 3 and 5 (SSH_MSG_KEX_DH_GEX_GROUP and SSH_MSG_KEX_DH_GEX_REPLY are sent by the server) technical-description
- RFC 3526 (published MODP safe primes usable as the worst-case input) technical-description
- security.alpinelinux.org vendor-advisory
- ENISA EUVD EUVD-2026-94165 third-party-advisory