Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-3935: CWE-502 Deserialization of Untrusted Data in ConnectWise ScreenConnect

0
High
VulnerabilityCVE-2025-3935cvecve-2025-3935cwe-502
Published: Fri Apr 25 2025 (04/25/2025, 18:27:44 UTC)
Source: CVE
Vendor/Project: ConnectWise
Product: ScreenConnect

Description

ScreenConnect versions 25.2.3 and earlier versions may be susceptible to a ViewState code injection attack. ASP.NET Web Forms use ViewState to preserve page and control state, with data encoded using Base64 protected by machine keys.  It is important to note that to obtain these machine keys, privileged system level access must be obtained. If these machine keys are compromised, attackers could create and send a malicious ViewState to the website, potentially leading to remote code execution on the server.  The risk does not originate from a vulnerability introduced by ScreenConnect, but from platform level behavior.  This had no direct impact to ScreenConnect Client. ScreenConnect 2025.4 patch disables ViewState and removes any dependency on it.

AI-Powered Analysis

AILast updated: 09/21/2025, 00:08:16 UTC

Technical Analysis

CVE-2025-3935 is a high-severity vulnerability affecting ConnectWise ScreenConnect versions 25.2.3 and earlier. The vulnerability arises from the use of ASP.NET Web Forms ViewState, a mechanism that preserves page and control state by encoding data in Base64 and protecting it with machine keys. The core issue is a deserialization of untrusted data (CWE-502) vulnerability, where if an attacker obtains the machine keys—requiring privileged system-level access—they can craft malicious ViewState payloads. These payloads can be sent to the vulnerable ScreenConnect web interface, potentially leading to remote code execution (RCE) on the server hosting the application. Notably, the vulnerability is not due to a flaw in ScreenConnect itself but rather stems from the underlying ASP.NET platform behavior. The ScreenConnect client is unaffected by this issue. The vendor addressed the vulnerability in ScreenConnect version 2025.4 by disabling ViewState entirely and removing any dependency on it, thus mitigating the risk. The CVSS v3.1 base score is 8.1, reflecting high impact on confidentiality, integrity, and availability, with network attack vector but requiring high attack complexity and no privileges or user interaction. No known exploits are currently reported in the wild.

Potential Impact

For European organizations using vulnerable versions of ConnectWise ScreenConnect, this vulnerability poses a significant risk. Successful exploitation could allow attackers to execute arbitrary code on the server, leading to full system compromise. This could result in unauthorized access to sensitive data, disruption of remote support services, and potential lateral movement within corporate networks. Given ScreenConnect's role in remote IT support and management, attackers could leverage this to gain persistent footholds or disrupt critical IT operations. The requirement for prior privileged access to obtain machine keys somewhat limits the attack surface but does not eliminate risk, especially if internal threats or other vulnerabilities exist that could lead to privilege escalation. The impact is particularly severe for organizations relying heavily on ScreenConnect for remote administration, including managed service providers and enterprises with distributed IT infrastructure across Europe.

Mitigation Recommendations

European organizations should urgently upgrade ConnectWise ScreenConnect to version 2025.4 or later, where ViewState is disabled and the vulnerability is mitigated. Until patching is complete, organizations should implement strict access controls to limit privileged system-level access, thereby reducing the risk of machine key compromise. Monitoring and auditing of privileged account activities should be enhanced to detect any unauthorized access attempts. Network segmentation should be employed to isolate ScreenConnect servers from less trusted network zones. Additionally, organizations can consider disabling or restricting access to the ScreenConnect web interface from untrusted networks and enforce multi-factor authentication for administrative access. Regular backups and incident response plans should be reviewed and tested to prepare for potential exploitation scenarios. Finally, applying ASP.NET security best practices, such as using custom machine keys with strong entropy and rotating them periodically, can further reduce risk.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
ConnectWise
Date Reserved
2025-04-25T14:32:25.365Z
Cisa Enriched
true

Threat ID: 682d983ec4522896dcbeff58

Added to database: 5/21/2025, 9:09:18 AM

Last enriched: 9/21/2025, 12:08:16 AM

Last updated: 10/16/2025, 12:51:12 PM

Views: 27

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats