RustDesk HTTP क्लाइंट हैंडशेक विफल होने के बाद अमान्य TLS प्रमाणपत्रों को चुपचाप स्वीकार करता है

The Improper Certificate Validation vulnerability in RustDesk Client creates a significant risk of man-in-the-middle (MitM) attacks. An attacker positioned between the client and the server can intercept and decrypt sensitive data, including session tokens, remote control commands, and potentially shared files. This could lead to unauthorized access to systems, data theft, and complete compromise of user accounts. The broad platform support (Windows, MacOS, Linux, iOS, Android) expands the potential attack surface considerably, impacting a wide range of users. The vulnerability's reliance on TLS retry mechanisms suggests attackers could exploit this by manipulating the TLS handshake process to present a fraudulent certificate.

Users of RustDesk Client who rely on the application for remote access and control are at risk. This includes individuals using RustDesk for personal use, as well as organizations deploying RustDesk for remote support or management. Specifically, users on networks with weak security controls or those connecting to untrusted Wi-Fi networks are particularly vulnerable.

• linux / server:

ps aux | grep rustdesk

• windows / supply-chain:

Get-Process -Name rustdesk

• generic web:

curl -I https://your-rustdesk-server.com | grep -i tls

1. 2026-03-05Disclosure

   disclosure

1. आरक्षित2026-03-05
2. प्रकाशित2026-03-05
3. संशोधित2026-03-17
4. EPSS अद्यतन2026-03-23

The primary mitigation for CVE-2026-30794 is to upgrade to a patched version of RustDesk Client. The vendor has not yet released a fixed version, so users should monitor the official RustDesk channels for updates. As a temporary workaround, consider implementing network-level controls to restrict access to RustDesk servers to trusted networks. Additionally, enforce strict certificate pinning policies where possible, although this may not be feasible for all deployments. Review RustDesk configuration to ensure TLS validation is enabled and configured with appropriate security settings. After upgrading, confirm proper certificate validation by attempting a connection and verifying the certificate presented by the server is valid and trusted.