Description
UltraVNC through 1.8.2.2 uses inadequate cryptography in the MS-Logon II authentication scheme (rfbUltraVNC_MsLogonIIAuth). In rfb/dh.cpp the Diffie-Hellman key exchange is performed with parameters that fit in an unsigned 64-bit integer (DH_MAX_BITS controls the prime size). A 64-bit DH key can be broken by Pollard's rho algorithm in under one second on current hardware. Additionally, the private exponent is generated by the rng() function, which multiplies three libc rand() values seeded from time(NULL). With approximately 31 bits of internal state and a time-based seed, the private exponent is recoverable in under a minute by a passive observer. A network attacker who can observe the MS-Logon II handshake (via sniffing, recording, or man-in-the-middle) can derive the shared DH key and decrypt the encapsulated username and password, resulting in full credential disclosure. This affects legacy MS-Logon II connections; MS-Logon III (X25519 + AES-256-GCM) is unaffected.
Published: 2026-07-01
Score: 7.4 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

UltraVNC versions up to 1.8.2.2 employ a two-party authentication scheme that relies on a 64-bit Diffie-Hellman exchange and a pseudo-random private key generated from three libc rand() calls seeded with the current time. The 64-bit modulus can be factored in under one second with Pollard's rho, and the nearly 31-bit internal state of the rand() sequence can be recovered by a passive observer in less than a minute. An attacker who can observe the MS-Logon II handshaking traffic—whether by sniffing, recording or a man-in-the-middle attack—can therefore derive the shared session key and decrypt the encapsulated username and password, resulting in full credential disclosure. The weakness is categorized as inadequate cryptography (CWE-326) and weak random number generation (CWE-338).

Affected Systems

The vulnerability affects the UltraVNC product line, specifically all releases through 1.8.2.2 that support the legacy MS-Logon II authentication protocol. Versions employing the newer X25519 + AES-256-GCM scheme (MS-Logon III) are not impacted.

Risk and Exploitability

The CVSS score of 7.4 indicates a high-severity flaw, and although an EPSS score is not available, the attack requires only passive network monitoring—something a threat actor can accomplish on any open network segment. The vulnerability is not listed in the CISA KEV catalog, but its mathematical weakness means a determined attacker can exploit it in minutes. Unless mitigation steps are applied, exposed services are susceptible to credential theft.

Generated by OpenCVE AI on July 1, 2026 at 13:07 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade UltraVNC to a version that implements MS-Logon III (X25519 + AES-256-GCM) or apply the vendor-issued patch that replaces the 64-bit Diffie-Hellman exchange.
  • If an upgrade is not immediately possible, disable the MS-Logon II authentication method or block incoming traffic on the service port using firewall rules.
  • Configure the environment to use a secure overlay network (e.g., VPN or SSH tunnel) when connecting to UltraVNC servers so that an eavesdropper cannot capture the handshaking packets.

Generated by OpenCVE AI on July 1, 2026 at 13:07 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 09 Jul 2026 05:30:00 +0000


Wed, 01 Jul 2026 14:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Wed, 01 Jul 2026 14:15:00 +0000

Type Values Removed Values Added
First Time appeared Uvnc
Uvnc ultravnc
Vendors & Products Uvnc
Uvnc ultravnc

Wed, 01 Jul 2026 05:00:00 +0000

Type Values Removed Values Added
Description UltraVNC through 1.8.2.2 uses inadequate cryptography in the MS-Logon II authentication scheme (rfbUltraVNC_MsLogonIIAuth). In rfb/dh.cpp the Diffie-Hellman key exchange is performed with parameters that fit in an unsigned 64-bit integer (DH_MAX_BITS controls the prime size). A 64-bit DH key can be broken by Pollard's rho algorithm in under one second on current hardware. Additionally, the private exponent is generated by the rng() function, which multiplies three libc rand() values seeded from time(NULL). With approximately 31 bits of internal state and a time-based seed, the private exponent is recoverable in under a minute by a passive observer. A network attacker who can observe the MS-Logon II handshake (via sniffing, recording, or man-in-the-middle) can derive the shared DH key and decrypt the encapsulated username and password, resulting in full credential disclosure. This affects legacy MS-Logon II connections; MS-Logon III (X25519 + AES-256-GCM) is unaffected.
Title UltraVNC MS-Logon II uses 64-bit Diffie-Hellman and seeded libc rand() enabling credential interception
Weaknesses CWE-326
CWE-338
References
Metrics cvssV3_1

{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: securin

Published:

Updated: 2026-07-09T04:35:51.099Z

Reserved: 2026-05-05T03:40:59.002Z

Link: CVE-2026-7830

cve-icon Vulnrichment

Updated: 2026-07-01T13:13:18.444Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-01T14:00:06Z

Weaknesses
  • CWE-326

    Inadequate Encryption Strength

  • CWE-338

    Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)